Nicolas Stucki

It seem that this issue started showing up with 756ae34f78435639a753c2326c472e04edf3bbc3. This change is probably making it easier to trigger another issue.

#### Minimal reproduction ``` sbt:scala3> testCompilation tests/neg/i8984.scala [info] Test run dotty.tools.dotc.CompilationTests started [info] Test dotty.tools.dotc.CompilationTests.parallelBackend ignored [info] Test dotty.tools.dotc.CompilationTests.negAll started [ ] completed (0/1, 0 failed, 0s)[info] Test dotty.tools.dotc.CompilationTests.runAll started...

I have no idea what is causing it yet. I suspect that the issue is in the reporter. We can patch the current failure on `main` temporarely if we delete...

As far as I can tell, this only affects `CompilationTests` and `BootstrappedOnlyCompilationTests`

The issue is that one of the reporters throws an exception. Furthermore, that exception throws an exception on `getMessage`.

To close this issue we need to - [x] Make sure that the test frameworks catches exceptions while reporting: #19566 - [ ] Reenable `tests/neg/i8984.scala`/`tests/neg/i8984.check` (disabled in #19561) and fix...

Also see https://github.com/lampepfl/dotty/pull/19245#issuecomment-1918597561

```scala def inline$valBinaryAPI2$i1(x$0: foo.G): Int = x$0.valBinaryAPI2 ``` should probably not receive `foo.G` as a parameter as it is statically known. We should probably generate ```scala def inline$valBinaryAPI2$i1: Int =...