breaking syntax changes! #24
Merged
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
- added parenthetical expressions
- arrays literals are now created with `Type.[item1, item2, itemn]`
- struct literals are now created with `Type.{
field1 = value1,
field2 = value2,
fieldn = valuen
}`
- array declarations (array types) and struct declarations have remained
unchanged, and the parser will detect and help correct older syntax
- few more little things + bug fixes
there are more changes I want to make but I'm keeping this commit to
syntax related changes only (other than a few bugs)
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.
Type.[item1, item2, itemn]Type.{ field1 = value1, field2 = value2, fieldn = valuen }there are more changes I want to make but I'm keeping this commit to syntax related changes only (other than a few bugs)