3 ms·
A horrible Javascript misfeature, second only to default global scope. I always use semicolons, but as the article notes even if you do that you still have to b
by orangecat 16y ago
A horrible Javascript misfeature, second only to default global scope. I always use semicolons, but as the article notes even if you do that you still have to be aware of how automatic insertion works.
- deleted 16y ago[deleted]
- notauser 16y agoFrom the article, the only really nasty things are: [a].forEach(fn(){}) [b].forEach(fn(){}) // Parses as [a][b] return a+b // Parses as return; You would have to work pretty hard to trigger the rest. I'm curious about the speed trade offs from removing semicolons. You shrink the source code a little, but does the parser throwing exceptions all the time bump up execution time?
- barrkel 16y agoA parser would not normally handle this kind of thing with exceptions, and any cost would only be paid once, at parse time when building a syntax tree, not at execution time. Very few languages interpret text directly, rather than interpreting trees, as the trees are far easier to work with, more efficient, etc.