2 ms·
> It took me an embarassingly long time to figure it out Granted it was 2013, don't sweat yourself. The code reads correct, compiles just fine, and it runs! N
by irjustin 2y ago
> It took me an embarassingly long time to figure it out
Granted it was 2013, don't sweat yourself.
The code reads correct, compiles just fine, and it runs! No clear error to hone in on.
These are some of the most difficult bugs with the "omg that's so dumb" response out the otherside. When everything appears correct, stepping through the data can take a long time because we know something is wrong but don't know which layer it's at.
- niborgen 2y ago> Granted it was 2013, don't sweat yourself. Don't worry, I don't. Funnily, recently something very similar happened. At work, there was this C++ class that had a 'void reset()' member function. Of course, at some point it was used with std::unique_ptr and we got some SIGSEGV. Took me a while to figure out that the '.reset()' was called instead of the '->reset()'. I think these 'omg that's so dumb' bugs are just part of programming.