Disallow inline methods and opaque types in same scope #6853
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.
It looks extraordinarily hard to me to mix opaque types and inline methods. Combining inline methods with private members was already hard, see
PrepareInlineable.scala
which deals with this. Combininginline methods with opaque types will be much harder. Quoting from #6846:
My current guess is that I'd need 2-4 weeks of full time work to arrive at a conclusion whether it's possible or not (I already spent 3 full days to arrive at this conclusion). But I don't have the time to do this. So it's safer we forbid this combination in an implementation restriction.
This PR also integrates the bits from #6846 that were worth salvaging.