Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using 'weight' instead of ' cost' #5

Closed
mindheist opened this issue Apr 17, 2016 · 0 comments
Closed

using 'weight' instead of ' cost' #5

mindheist opened this issue Apr 17, 2016 · 0 comments

Comments

@mindheist
Copy link

I guess the original authors might have to take a look to decide this . But In the implementation of Graphs, can we just use "weight" instead of "cost". I suppose most readers would ofcourse understand that its conceptually the same , but I guess it would be more homogenous if the book used 'weight'


    def addEdge(self,f,t,cost=0):
        if f not in self.vertList:
            nv = self.addVertex(f)
        if t not in self.vertList:
            nv = self.addVertex(t)
        self.vertList[f].addNeighbor(self.vertList[t], cost)

    ```

http://interactivepython.org/runestone/static/pythonds/Graphs/Implementation.html
@bnmnetp bnmnetp closed this as completed in 31d20c2 Sep 6, 2019
jdeisenberg pushed a commit to jdeisenberg/pythonds that referenced this issue Jul 25, 2023
replaced the word "cost" with the word "weight."

closes RunestoneInteractive#5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant