Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/486
The `PathProcessor` interface has no function for SimpleStep and doesn't
add any overhead. AFAIK `PathProcessor` is only used by strategies to easily
identify traversals with "special requirements". Both, `SimpleStep` and
`CyclicStep`, access the current `traverser.path()` and thus they **process**
the **path**, which makes them `PathProcessor`s :).
I can also rely on the result of `getRequirements()`, but this would make
the strategy a bit slower and I really don't see why `SimplePath` and
`CyclicPath` should not be `PathProcessor`s.
---
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.
---
