Closed
Description
If I abort in the middle of a build I often get errors like this:
Tasty UUID (00c95233-db90-de00-00bb-2b5192afb400) file did not correspond the tasty UUID (007e6fd1-1df0-ff00-0051-207d11d1f200) declared in the classfile /Users/odersky/workspace/dotty/community-build/community-projects/scalatest/scalatest.dotty/target/scala-0.25/classes/org/scalatest/tools/StringReporter.class.
These errors are sticky. Rebuilding will come back with the same ones. I have to do a clean to make them go away.
Expectation
I think these errors should be handled better. If it's the wrong Tasty UUID, pretend it is not there and assume the class file is missing also, returning a stub symbol.
At the very minimum, add a note to the error that this requires a clean. But the note should really not be necessary, it's better to handle the problem at the root.