[SE-0341] Restrict opaque type parameters in consuming positions. #1545
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.
Per discussion on the review thread, restrict the use of opaque type
parameters in "consuming" positions. They are not useful here (because
it's hard to create values to pass when you don't have access to the
type), and this follows the reasoning in SE-0328 for the same
restriction. Add a Future Directions section to talk about "flipping"
the generics for opaque types in consuming position.