2 ms·
I don't get this approach, it's backwards. Why can't the JIT assume everything is perfect and spit out information like: Warning: Can't optimize function foo in
by noiv 12y ago
I don't get this approach, it's backwards. Why can't the JIT assume everything is perfect and spit out information like: Warning: Can't optimize function foo in bar.js because of foobar? Instead devs have to tell the JIT what to assume and wait for errors.
What I'm missing here?
- colinramsay 12y agoThis would make more sense to me, if not only because it seems like a great way to avoid the most complained-about parts of JavaScript, like weird type coercion.