In Scala 3 TASTy reader, restrict access to experimental definitions #10020
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
experimental definitions are treated like compileTimeOnly. Test that a scala 3 application can not depend on a scala 2 library that uses experimental definitions.
bishabosha
force-pushed
the
tasty/support-experimental
branch
from
2603a75
to
45f1f38
Compare
|
fixed JavaUniverseForce |
dwijnand
approved these changes
May 5, 2022
SethTisue
changed the title
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.
experimental definitions are treated like compileTimeOnly.
Test that a scala 3 application can not depend on a scala 2
library that uses experimental definitions.
There is a modification to
RefChecksto add@experimentaltocheckUndesiredProperties- also I seem to have uncovered a bug inRefCheckswhere it will not checkFooinList[Foo]().