←back to thread

32 points matt_d | 1 comments | | HN request time: 0.355s | source
Show context
orlp ◴[] No.45138254[source]
Every developer I've talked to has had the same experience with compilation caches as me: they're great. Until one day you waste a couple hours of your time chasing a bug caused by a stale cache. From that point on your trust is shattered, and there's always a little voice in the back of your head when debugging something which says "could this be caused by a stale cache?". And you turn it off again for peace of mind.
replies(3): >>45159702 #>>45159758 #>>45160578 #
1. ACCount37 ◴[] No.45160578[source]
Don't you just do "flush the cache, rebuild" at the first suspicion? If the bug abruptly goes away, it was stale cache. It usually doesn't.