Native macros #21
Merged
Native macros #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
...so that lookups for simple types can be done first
Passing t.next in iterator callback resulted in stale data, but it's
really not needed, so we drop it and use value interface{} and construct
a shaddow Tree for mergin source onto the target
TODOs
|
...and keywords to macros
errordeveloper
force-pushed
the
key-based-expressions
branch
from
a3641dc
to
fa8bffe
Compare
errordeveloper
force-pushed
the
key-based-expressions
branch
5 times, most recently
from
9ecb48e
to
3a7af6f
Compare
- allow overlaying arrays over emptied objects and empty arrays - pass poiters to slice in *t.keyTypeSwitch - all lookup macros done in the same phase
errordeveloper
force-pushed
the
key-based-expressions
branch
from
3a7af6f
to
1ad5aea
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR wraps up the improvements to macro processing code. Using jsonparser was just a bit too painful as it stores the tree as byte buffer internally which can be tricky to work with.