Dear Apache TinkerPop Community, I’ve just created a pull request with a proposal that seeks to clarify expectations and guarantees around lazy vs. eager evaluation in Gremlin:
* https://github.com/apache/tinkerpop/pull/2898 The proposal primarily calls for changes in the documentation and Gremlin Feature Tests where execution order expectations are more assumed than explicit. It also suggests to change the side effect version of aggregate() w.r.t. to its scope, in order to align it with other side effect steps. Looking forward to feedback and a discussion with the community! Best, Michael Schmidt
