generate component specific grammars#181
Merged
Merged
Conversation
Closed
6d4aed4 to
aafab8a
Compare
…s array-style as in v2/toml. should rather generate grammars from v1 dfns.
a7b577d to
ebf53b9
Compare
be181c7 to
66a59b2
Compare
2421afd to
c18d442
Compare
c18d442 to
e244352
Compare
e244352 to
75075f7
Compare
7e5177f to
b1b4283
Compare
This file contains hidden or 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
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.
rough first cut at a reader supported by typed grammar generation. typed parser/transformer working for a few test pkgs. period data is just defined in terms of nondescript records, everything else is properly defined. maybe eventually we can properly type record fields. I included generated grammars here for now so we can easily see what they look like. but maybe at some point it will be cleaner not to version them.