3 ms·
> ! is not intended to be a statement separator. ; is. Which is why there is a line break there. He's far too stubborn to realize that JSMin is at fault for no
by Sephr 15y ago
> ! is not intended to be a statement separator. ; is.
Which is why there is a line break there. He's far too stubborn to realize that JSMin is at fault for not being able to correctly parse JavaScript.
- jpeterson 15y agoThe line break will not help if ! becomes an infix operator.
- jurre 15y agoBut as of now it's not.
- erichocean 15y ago! is already being discussed to be turned into an infix operator in a future version of JavaScript.
- deleted 15y ago[deleted]
- Sivart13 15y agoFuture versions of JavaScript might also replace the 'function' keyword with a picture of a chicken, but I'm still going to keep typing the word 'function' for now.
- deleted 15y ago[deleted]