Clarify local() side-effect state semantics with a runnable example - #3676
Merged
Merged
Conversation
Add an executable example to the local() step in the Gremlin semantics specification and expand its Considerations to distinguish the local computational state that is reset between executions from global side-effects such as aggregate() and store(), which accumulate across every traverser and are not reset per incoming object. Assisted-by: Kiro:claude-opus-4.8
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3676 +/- ##
============================================
+ Coverage 76.35% 76.69% +0.33%
- Complexity 13424 14336 +912
============================================
Files 1012 1037 +25
Lines 60341 64761 +4420
Branches 7075 7695 +620
============================================
+ Hits 46076 49671 +3595
- Misses 11548 11998 +450
- Partials 2717 3092 +375 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add an executable example to the local() step in the Gremlin semantics specification and expand its Considerations to distinguish the local computational state that is reset between executions from global side-effects such as aggregate() and store(), which accumulate across every traverser and are not reset per incoming object.