Utility functions to create an edge_src|dst_property view objects. #5078
Conversation
This file contains hidden or 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
seunghwak
added
improvement
ChuckHastings
approved these changes
May 19, 2025
jnke2016
approved these changes
May 19, 2025
|
/merge |
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.
In SG, the vertex range of edge source/destination property values coincide with the local vertex partition size; so, creating owning data structures for both vertex property values & edge source|destination property values waste memory.
Users can directly call detail::edge_endpoint_property_view_t constructor functions to avoid this (this was considered as tricks for advanced users). To make this easier, this PR adds non-detail space utility functions.