-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #8020: Create dotty-tasty-inspector library #8021
Conversation
7bfbd64
to
e34a01f
Compare
What's the benefit of having an extra library instead of having this stuff in dotty-compiler ? |
Same as in |
To make things simpler we could fusion dotty-staging and dotty-tasty-consumer then. |
|
c814ac9
to
9485a20
Compare
9485a20
to
6185481
Compare
I'm considering renaming it |
fe1f9ad
to
486c184
Compare
Also rework TastyInspector API to simplify use.
486c184
to
83fc85a
Compare
Repeats the changes in #7080 for
dotty-tasty-inspector
.Extract the tasty-consumer out of the standard library and compiler.
dotty-tasty-inspector
project that depends ondotty-compiler
dotty-tasty-inspector
project or jartasty.file.{ConsumeTasty, TastyConsumer}
,TastyConsumerPhase
, andTastyFromClass
intodotty-tasty-inspector
asTastyInspector
ConsumeTasty.apply
directly (instead of as a java reflection call) asTastyInspector.inspect
"ch.epfl.lamp" %% "dotty-tasty-inspector" % scalaVersion.value
dotty.tools.dotc.util.ClasspathFromClassloader
core logic fordotty-staging
anddotty-tasty-consumer
tastdoc
tests on CI (mostly to check it compiles)