Update tuple syntax to use {..} instead of (..) and allow named fields
#138
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
mohammadfawaz
force-pushed
the
mohammadfawaz/137
branch
3 times, most recently
from
01218d5
to
1800794
Compare
mohammadfawaz
changed the title
{..} instead of (..){..} instead of (..) and allow named fields
mohammadfawaz
force-pushed
the
mohammadfawaz/137
branch
from
1800794
to
77c4e8d
Compare
mohammadfawaz
force-pushed
the
mohammadfawaz/137
branch
from
77c4e8d
to
3e78dfe
Compare
This was referenced Jul 28, 2023
mohammadfawaz
changed the title
{..} instead of (..) and allow named fields{..} instead of (..) and allow named fields
otrho
approved these changes
Jul 31, 2023
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.
Closes #137