> A stack trace is still better than a one line error with no context. It's a kind of 80% solution - it's not ideal (a perfect error includes only the relevant

> A stack trace is still better than a one line error with no context. It's a kind of 80% solution - it's not ideal (a perfect error includes only the relevant context), but getting it's much better for 0 effort than error codes/values give you for free. Yeah, a stack trace is better then an “undefined error” type message. But the point of forcing error messages over exceptions is you’re enabling you’re developers to write meaningful error messages. So your point is moot. > So what is the profound difference between doing input validation in your own code vs letting the array accessor do it? - Meaningful error messages (eg has the code failed because of a bug or because of invalid user input?), - security hardening, - reducing potential undefined behaviours, - thorough unit testing, - self documenting code (the code clearly defines what the happy path is and when it’s possible for a user to break out from that) Etc