Hi,
> LocalMachine, it will lookup the registered UUID and if it exists, use the
> pre-compiled source code.
So what Machine.register() does generally, is up to the implementation.
LocalMachine.register() does what TP3 does in TraversalSource. It
“pre-compiles”.
- sort strategies
Hi,
One point of clarity.
You might ask:
“Why not just sort strategies in TraversalSource like in TP3? — like
DefaultTraversalStrategies.class”
Answer:
TraversalSource is Gremlin-specific. TP4 is seeing Gremlin as simply an
implementation of the Builder-pattern for Bytecode.
> Now when bytecode (containing instructions for execution) is submitted to
LocalMachine, it will lookup the registered UUID and if it exists, use the
pre-compiled source code.
maybe i didn't follow properly but is this for the purpose of caching
traversals to avoid the costs of traversal to bytec
0. Asciidoctor is not Asciidoc (applications)
This was not immediately obvious to me when I started. I have found that
Asciidoc renders the following scenarios correctly. However, our maven
build uses Asciidoctor which rendered incorrectly. So if you write
asciidoc and use some tool to preview c
