Merged
Conversation
084559a to
62285a3
Compare
Which receives type arguments.
* Validate regularity of gneeric type aliases * Validate generic type alias applications
bdce8e0 to
5b8d20a
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
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 adds the key feature for RBS 1.8, generic type alias!
You can now define generic type aliases like:
We also provide new
DefinitionBuilder#expand_aliasvariants to unfold a type alias:#expand_alias1and#expand_alias2.So, the type checkers will continue working if no generic type alias is used in the application. Or, you can just replace your
#expand_aliascalls with#expand_alias1for the minimal support.Generic type alias also supports variance annotations.
One limitation of defining generic type alias is the regularity. It prohibits polymorphic recursion. You cannot use a type alias polymorphic in its declaration.
syntax.md