Rewritten Var/values implementation based around flexbuffers #371
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This basically rewrites most of the values layer to be based around values and collections held in flexbuffers. (Flexbuffers are part of the flatbuffers project, and are a kind of zero copy dynamic flatbuffer.)
Part of a bigger effort to do the following:
Along with this change came major cleanups generally to the interface in the values layer:
compiler
crate, making it clear that the literal printing is of a MOO value, and leaving room for other languages to have other representations, or to add different pretty printing / decompilation options.To be done still: