List literal with refs: parse [a b c] as 3-element list#167
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
danieljohnmorris
force-pushed
the
fix/list-literal-refs
branch
5 times, most recently
from
0361771 to
806e553
Compare
tests + example covering the case.
danieljohnmorris
force-pushed
the
fix/list-literal-refs
branch
from
806e553 to
1b1470f
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
1 participant
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.
Two personas hit
[a b c]parsing asCall(a, b, c)instead of a list of three refs. Asymmetric with[1 2 3](numeric) which already worked. Disambiguation: if the list has top-level commas, treat as expression list; otherwise treat bare refs as list elements.[(f x) y]still works for explicit calls. Cross-engine tests + example.