[docs] Context bounds in polymorphic functions targets 3.7 #21822
Conversation
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
|
Overall makes sense. There is another issue though regarding the examples in the docs. My current implementation doesn't lift the restriction of requiring at least one term parameter list in a poly function type. And so the alias example is rejected in parser right now. When discussing it last time, we decided to leave it as a future improvement for now. This isn't relevant to changing the target version for this change, but just wanted to mention it somewhere. |
KacperFKorban
approved these changes
Oct 23, 2024
|
Seems to be no longer applicable: #21643 (comment) |
|
this is no longer true |
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.
[skip-ci]