However, I am unsure of the next steps in mitigating or avoiding this issue. Are there any recommended solutions, workarounds, or ongoing efforts to fix this problem? This issue severely impact the development experience, as it makes it difficult to accurately identify and address compiler errors
I am encountering an issue when using munit in Scala3, where the compiler error messages are always shadowed by the following message:
This issue seems to be well-known, as it was reported and fixed in the Dotty repository (https://github.com/lampepfl/dotty/issues/9685), and if I understand correctly is covered by the munit test suite (https://github.com/scalameta/munit/blob/8558ab134313c30f94936c5a1ca5596bda4d6c67/tests/shared/src/test/scala/munit/AssertionsSuite.scala#L196).
However, I am unsure of the next steps in mitigating or avoiding this issue. Are there any recommended solutions, workarounds, or ongoing efforts to fix this problem? This issue severely impact the development experience, as it makes it difficult to accurately identify and address compiler errors
I've created a small repository to demonstrate the issue: https://github.com/alessandrocandolini/munit-clue-confusing-suggestion. If i can help in other ways, please let me know
Thank you