3 ms·
Looking at an object in my debugger back in my call stack and assume I'm looking at the value as it was but in reality it was mutated in a subsequent stack give
by slifin 2y ago
Looking at an object in my debugger back in my call stack and assume I'm looking at the value as it was but in reality it was mutated in a subsequent stack gives me trust issues
It's probably fine most of the time it's just when I have to get into the weeds I want to have stability
- throwaway96666 2y agoThat seems like a debugger problem, can't the debugger clone/maintain history of the object?