3 ms·
I guess what chrisjj might have meant is that "debugging" usually starts with a bug, a or symptom. So in case of debugging the standard library, it usually is a
by pipo234 3y ago
I guess what chrisjj might have meant is that "debugging" usually starts with a bug, a or symptom. So in case of debugging the standard library, it usually is a problem in your own code that you cannot explain and try to blame on an error of the subsystem. In those cases, having access to a source-level debugger can be useful but in my experience this the subsystem is usually not where you'll find the error; more often it's in your own code.
So in case of this article, ask: what is the symptom of an alleged bug in the standard library that the author is trying to uncover?
This article is more about using the online debugger to explore parts of the standard library. Which is interesting, but as others have pointed out probably not the best way to familiarize yourself with a language or library.
- account42 3y ago> but in my experience this the subsystem is usually not where you'll find the error; more often it's in your own code More often perhaps, but compilers and their standard libraries are complex pieces of software written by human beings - and it's not that uncommon to encounter them, especially if you go a bit off the beaten path or are an early adopter.
- pipo234 3y agoSure, that happens too. And it would be interesting to read an article about that; but that is not what this article is about despite its title :-)