> Checking the bug mentioned, it was fixed in 2022.

I was considerably less impressed by the reporting when I finally found out the culprit.

Sure it was “Scala 3” … but not really.

It was an interaction of factors and I don’t think it would take away from the story to acknowledge that up front.