4 ms·

I'm curious. Can you go into more detail what kind of bug it found?

• airstrike 2y ago
  I was writing a custom widget for iced (the Rust GUI library) and I was getting a panic due to some fancy logic I was trying to do. I guess the shortest description I can say is that it was a combination of what appeared to be a caching issue at first, but the real cause turned out to be some method shadowing where I was using a struct's method where I meant to use the trait's method. I had made the specific operation generic (moving it out of the struct and into a trait) but forgot to delete it from the struct, so I was calling the incorrect function. Claude pinpointed the cache issue immediately when I just dumped two files into the context and asked it: somewhere in my codebase I'm triggering a perform() on the editor but the next call on highlight() panics because `Line layout should be cached` what am I missing? do I need to do something after perform() to re-cache the layout? at first that seemed to fix the issue, but other errors persisted. so we kept debugging together until we found the root cause. either way I knew where to look thanks to its assistance