> Is it standard in interpreted language land to avoid optimizations in case for the debugger use case? Yes. Otherwise, you'd have to have separate "being deb

> Is it standard in interpreted language land to avoid optimizations in case for the debugger use case? Yes. Otherwise, you'd have to have separate "being debugged" and "not being debugged" runtimes that keep track of different information and do different things, and it's not unlikely that you'd end up with programs doing different things as a result. You can actually access debugger information from inside the program, and it's not that uncommon to do that.