-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
VertexAttributes func caching last values #177
Comments
tzq0301
added a commit
to tzq0301/graph
that referenced
this issue
Jun 15, 2024
tzq0301
added a commit
to tzq0301/graph
that referenced
this issue
Jun 15, 2024
tzq0301
added a commit
to tzq0301/graph
that referenced
this issue
Jun 15, 2024
tzq0301
added a commit
to tzq0301/graph
that referenced
this issue
Jun 15, 2024
tzq0301
added a commit
to tzq0301/graph
that referenced
this issue
Jun 15, 2024
…the user, preventing two maps from actually being the same reference (issue dominikbraun#177)
tzq0301
added a commit
to tzq0301/graph
that referenced
this issue
Jun 15, 2024
…the user, preventing two maps from actually being the same reference (issue dominikbraun#177)
tzq0301
added a commit
to tzq0301/graph
that referenced
this issue
Jun 15, 2024
…the user, preventing two maps from actually being the same reference (issue dominikbraun#177)
redVertexAttr = graph.VertexAttributes(map[string]string{"color": "red"}) This was a bug of the library, and I fixed it in PR #179, cc. @dominikbraun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Calling AddVertex() with VertexAttribute() functions will sometimes cache the last value on all vertices. I've been unable to reproduce this via your unit tests, but this shows the issue:
Each vertices' Attributes map contains the Attributes of the last created vertex. Am I creating these VertexProperties functions incorrectly, or mis-using them?
The text was updated successfully, but these errors were encountered: