Avoid infix, tuple, and function syntax when using kind-projector #3209
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 is more a question than a proposal, I guess. I'm working on
-Ykind-projector
for Dotty, and I have a WIP implementation that I've confirmed can compile cats-core after #3207, #3193, and the change here (and one big Simulacrum rewrite).I think it makes sense to try to minimize the scope of Dotty's kind-projector compatibility, and right now my implementation only handles the type-level
λ[x => ...]
syntax and*
in ordinary type application (F[A, *, B, *, C]
). This is a really tiny change—around 50 lines in the parser behind a singleif (ctx.settings.YkindProjector.value)
. Adding support for*
in tuple types, function types, and infix types would be a lot more invasive.Maybe we should do it anyway, but for Cats at least only supporting
*
in type application isn't a very painful limitation—it only requires the changes here, and I think some of these changes (likeA Ior *
toIor[A, *]
) are readability improvements, anyway.