Reword reference article about type projection so that it highlights what is allowed #22793
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
This commit only exists to avoid git being confused, it is not independent of the following commit !
…what is allowed Was previously focused on what was forbidden/dangerous which made it feel like an unsafe feature
|
Things I did not have time/the knowledge to do:
|
odersky
reviewed
Mar 13, 2025
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.
Was previously focused on what was forbidden/dangerous which made it feel like an unsafe feature
See for example: https://users.scala-lang.org/t/path-dependent-types-accessing-outer-class/10620/8
I left the paragraph about "type-level encoding of a combinator calculus" but it feels more like trivia than useful information ?