Did you know that JavaScript allows for unicode escape literals in identifiers? This is actually valid js: `var \u0074hing, \u0073tuff`. That leads to parser code that looks like this: https://github.com/FreeMasen/RESS/blob/9351637a814d33840ded75a80bace40b03d5eac5/src/tokenizer/keyword_escape.rs …
That approach is inherently broken. There’s an infinite number of \u{…} escape sequences for each code point. For example, these: \u{6F} \u{6f} \u{06F} \u{06f} \u{006F} \u{0006F} \u{00006F} …all represent the same code point.
-
-
Oof! The match is really just a stop gap solution
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.