3 ms·
The point I'm making here is that everyone knows 1!=2. It's not helpful for a test to tell you that because then you have to go hunting around to figure out wha
by it 9y ago
The point I'm making here is that everyone knows 1!=2. It's not helpful for a test to tell you that because then you have to go hunting around to figure out what is wrong instead of it just giving you at least a rough idea right away. It does not depend on what you're used to.
- tyingq 9y agoI get that part. I'm saying Go doesn't fix stupid either. I can panic 6 layers into a dependency chain with a verbose error message that helps nobody. It's often easier to fix 1!=2 if I know the entire error stack than it is to know exactly what happened where, but not the path down. Like as obtuse as 1!=2 is, with exceptions, I might more easily recognize it as a reference leak.