Sébastien Doeraene

Not really. What we want to get rid of is `Obj == x` (Scala's equality) for pattern matching. But `==` is not always reference equality. For example `Nil == Vector.empty`....

Unfortunately, your analysis is slightly off, and your suggestion is relatedly not at all easy to implement. (In fact, it would be easier to implement something where the optimizer figures...

> I don't think Scala or Scala.JS have a purity analysis. Scala.js has a limited side-effect-free analysis in its optimizer. Currently it is mostly useful to get rid of useless...

Now that Infos are computed at link-time (#3078), this does not need to be in by 1.0.0.

AFAIK, there is no way to force that using configuration. The only way is to execute the tests of each project in a separate sbt command. Browsers will be cleaned...

@gzm0 So, is this as-designed/won't fix?

Querying all subclasses on an instantiatable class (or *all* instantiatable classes for that matter) is something we could expose easily as a library-level new method in `Reflect`. Querying by annotations...

> If it's OK with you, I'd like to keep this open for a bit and think a bit more. Sure.

Technically, the bootstrapper contains everything we would want, including the ability to iterate over all the tests, for discovery. The problem is that a generic processor would have to work...

No, only testing frameworks that rely on an `AnnotatedFingerprint` would require this. And today, those testing frameworks require a compiler plugin anyway. Moreover, in practice, we only know of JUnit...