Use :orn instead of :altn for map destructuring#1019
Merged
Conversation
mx/defn destructuring => spec problem:multi instead of :altn for map destructuring
:multi instead of :altn for map destructuring:orn instead of :altn for map destructuring
:orn instead of :altn for map destructuring:orn instead of :altn for map destructuring
:orn instead of :altn for map destructuring:orn instead of :altn for map destructuring
Member
|
makes sense! |
fdf3fa4 to
ead1d01
Compare
ead1d01 to
ce586a6
Compare
:orn instead of :altn for map destructuring:orn instead of :altn for map destructuring
Contributor
|
+1 |
Member
|
Good catch, thanks!! |
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.
Related #1020
Map destructuring shouldn't convert to an
:altnbecause it turns into a sequence spec when nested::ornis better for the job here: