Jerry Tan

@SethTisue I am unfamiliar with Scala compiler, would you say this is a compiler issue? As in OP's reproduction, `Foo` is invalidated after `Foo` is changed, but nothing depends on...

> The 3 large binary files clearly don't belong into this repo but I don't know what's the right place for them. They are used by the integration tests and...

> I added the test cases in [dotty-staging/dotty@304c41a](https://github.com/dotty-staging/dotty/commit/304c41a714a50016b443c87640081a0eb479682f), which fail, so we would need to reimplement the logic in Scala 3 - is there a special reason to introduce the...

Thanks. I will look into that case. I don't fully understand why `A1.scala` would not be invalidated anyways in the next cycle when `invalidateAfterInternalCompilation` is called. But I guess playing...

> Running `mvn clean install deploy` ends up in an endless compilation loop in the sansa-sabine module (sansa binding engine). Might be related to [sbt/sbt#6183](https://github.com/sbt/sbt/issues/6183) In any case, it would...

> Currently, macro annotations are expanded in the inlining phase, which happens after the API phase. If we wanted to solve this we would have to collect some information about...

Referring to sjrd's comment > Attempting to compile *any* project using Scala 2.12.4 and sbt 1.6.0+, including a Hello World, results in a StackOverflow. Therefore, no one must be using...

I'm reviewing this issue and am interested in the setup used for profiling `lookupAnalysis`, specifically the projects with long classpaths where `lookupAnalysis` is prominent in benchmarks. I'm currently working on...

#475 is passing after #1284 Since the cause of the issue, as mentioned, is: > The actual error happening here has more to do with scalac, and the breaking of...

> The `inline` annotation is not required. Yeah... I honestly thought that https://github.com/sbt/zinc/pull/1310 would cut it, until I tested the PR fix against 2.13.12... > Also, everyone is 5 years...