changed storing list of strings to list of tuples of strings #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdindoost
pushed a commit
that referenced
this pull request
Jul 20, 2024
changed storing list of strings to list of tuples of strings
mdindoost
pushed a commit
that referenced
this pull request
Dec 3, 2024
changed storing list of strings to list of tuples of strings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The storage for properties used to be as a string delimited by a colon as such: "property_name : property_value" this was updated in Chapel to be a tuple instead as such: (property_name:string, property_value:string) this way we can extract property_name and property_value without first splitting the string.
Further, in Utils.chpl we updated the print_graph_serverside() function to handle the new updated data structure for node and edge properties.