Aliasing #2301
Merged
Aliasing #2301
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
Closed
janmasrovira
force-pushed
the
2188-aliasing
branch
2 times, most recently
from
760d17d
to
cef19f0
Compare
Closed
janmasrovira
force-pushed
the
2188-aliasing
branch
from
9305f69
to
0844492
Compare
janmasrovira
force-pushed
the
2188-aliasing
branch
from
762b7fd
to
eb20dfd
Compare
lukaszcz
approved these changes
Aug 25, 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.
This pr introduces a new syntactical statement for defining aliases:
where
oldNamecan be any name in the expression namespace. Fixity and module aliases are not supported at the moment.newNamedoes not inherit the fixity ofoldName. We have agreed that the goal is to inherit the fixity ofoldNameexcept ifnewNamehas a fixity statement, but this will be done in a separate pr as it requires Supportnonefixity #2310.