Sébastien Doeraene

Yes, I think you're right. Although `getSuperclass` wouldn't be enough. We would also need `getInterfaces`, which we never implemented. And even then, it wouldn't work with altered ` runtimeClassName`. So...

Yes, the big downside is that it would require recompilation of the superclass/supertrait (so in practice, of the testing framework) for this feature to work. The question is: is that...

No, that would not be the equivalent. We don't need to recompile test classes. We only need to recompile the superclass/supertrait of all tests, which is defined in the testing...

We can't really do that, I'm afraid. First, in terms of binary compatibility, that would break every testing framework that has been published. We would have a hard time to...

Oh, you're aiming far! Wow. That will require to get even more people on board, notably the maintainers of all the Scala build tools in circulation. I guess the right...

Perhaps we should have a larger discussion with likely stakeholders, such as build tool maintainers and testing framework maintainers. It seems we're not going to achieve anything on our own,...

This is needed for memory management. We should release references to `a` as soon as possible so that any memory that `a` holds on to can be reclaimed by the...

We should at least figure out now how we are going to represent that information in the IR. Could they be two additional flags in the `ApplyFlags` of `Apply*` nodes?...

Thinking more about this, I'm confident we can use the `ApplyFlags` for this purpose, so delaying to post-v1.0.0.

Unfortunately, I still consider the lack of decent support for binpacking a serious problem with scalafmt for this codebase. The changes in `compiler/` and in `OptimizerCore.scala` are really bad, for...