Burst cache remembers old versions of classes

[pastel sparrow]

Every now and then when low on disk memory the burst compiler silently generates corrupt methods, and it won't get fixed until the burst cache is cleared or the method is modified so it recompiles it.

However it appears that if you change the method and make a build, then revert the method to the original version and make another build, the burst cache still remembers the old corrupt version. Is this intentional or a bug?

[grand snow]

Burst cache failing to notice changes has been a problem forever

It's slowly improved over time, but there's still a ton of different ways to trigger it