Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/842
I'm ok with either direction - either to only support types symmetrically
or try to support at the reading site as much types as possible - as long as we
make that decision clear and follow it consistently for all GLVs.
Could we then somehow mark types as deprecated that we identify as
problematic for non-Java languages? That would make it clear to users that they
can expect types like `byte` or `char` to be supported across GLVs, but that
they should avoid using types like `Instant` or `YearMonth`.
Otherwise users basically have to check the source code of the GLV(s)
they're using when they want to know which type they can use and even if it's
not implemented they can't know whether it was omitted on purpose or if the
implementation is just still missing.
---
