3 ms·
I'm sure there are existing systems for which this is quite involved. These are design choices, though. If the compiler can figure it all out and find everythin
by Firadeoclus 5y ago
I'm sure there are existing systems for which this is quite involved. These are design choices, though. If the compiler can figure it all out and find everything, then so can an IDE, and make everything visible where it needs to be visible.
- samus 5y agoThe issue is that it can become very complicated very quickly, even when the IDE is able to figure it all out and present it in a useful way. Even with the best tooling, nonlocal control flow can't help but increase the WTF per minute[0]. [0]: https://www.osnews.com/story/19266/wtfsm/ https://www.osnews.com/story/19266/wtfsm/
- Firadeoclus 5y agoIf it does in fact become "very complicated" then maybe you are trying to achieve something that is very complicated. Good tooling takes the surprise out of nonlocal control flow, and can project it into local control flow on demand. To take it back to skrebbel's complaint, "methods defined far, far away", "absolutely no way to tell", "very surprising", "no indication whatsoever" -- all things that good tooling fixes because it can show you what gets injected where and why, when you need it (and show you a minimally intrusive reminder when you don't).