Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/485
Why add methods to `Traversal`? Why add a new `TraversalStrategy`? To solve
this problem in particular, why not just "walk right" and if you see a "lazy
side-effect" like `StoreStep`, then turn trigger a flag in
`LazyBarrierStrategy` to not apply barriers. You can then turn back on the flag
if you there are no more steps that introspect into the side-effect.
For example:
`g.V().out().out().store('a').out().out().cap('a').out().out()`
This would compile to:
`g.V().out().barrier().out().barrier().store('a').out().out().cap('a').barrier().out().barrier().out()`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
