Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/564
@dkuppitz asked me to say more of my thoughts on the matter.
I think we need a general theory for how we are going to handle primitive
manipulations. That is, math operators, string operations, character
operations, type casting operations, etc.
If we just append this feature for `Strings` then we might end up
backtracking come a more general theory. It just seems that this PR is a "this
would be cool" and implemented. Not: "So, primitives all fit this style of
manipulation in a flow-based system..."
Questions that arise:
* What about `unfold()`? Now we are in character manipulation or just
single character strings?
* What about `fold()`? Does character folding become strings?
* What about `range()` on doubles/floats? Is that a way to clip precision?
I don't think we should just add this PR without a fully thought through
model for all primitives and how they will be effected by the current or "need
to be built" steps.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
