-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Avoid overcompilation involving inline or annotation trees #8359
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
Conversation
test performance please |
performance test scheduled: 1 job(s) in queue, 0 running. |
Performance test finished successfully: Visit http://dotty-bench.epfl.ch/8359/ to see the changes. Benchmarks is based on merging with master (228e593) |
test performance with #sbt please |
performance test scheduled: 1 job(s) in queue, 1 running. |
Performance test finished successfully: Visit http://dotty-bench.epfl.ch/8359/ to see the changes. Benchmarks is based on merging with master (811dc19) |
@@ -624,6 +623,6 @@ private class ExtractAPICollector(implicit val ctx: Context) extends ThunkHolder | |||
// junit tests are annotated @org.junit.Test). | |||
api.Annotation.of( | |||
apiType(annot.tree.tpe), // Used by sbt to find tests to run | |||
Array(api.AnnotationArgument.of("FULLTREE", annot.tree.show))) | |||
Array(api.AnnotationArgument.of("FULLTREE", annot.tree.toString))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment above also needs to be updated
We used to pretty-print trees in the API info we send to sbt, but the pretty-printed output seems to be unstable leading to overcompilation, so just use the raw trees instead (this should also be faster).
de03284
to
b952d41
Compare
We used to pretty-print trees in the API info we send to sbt, but the
pretty-printed output seems to be unstable leading to overcompilation,
so just use the raw trees instead (this should also be faster).