@mathias I just discovered that the `Name=` property was left out of the Unicode property escape proposal. That's kinda disappointing. The benefit would be readability. https://github.com/tc39/proposal-regexp-unicode-property-escapes/commit/51395543dbcf7574b40689f9d49d651097ec6817 … Any chance of seeing it in a follow-up proposal?
-
-
\p{Name=…} offers a strictly smaller benefit than \p{Property=Value} or \p{Sequence} (https://github.com/tc39/proposal-regexp-unicode-sequence-properties …). Given that, I’m personally not convinced it pays for itself given the binary size cost it would incur.
-
What do you mean by "binary size cost"? Are you talking about the JS source code size? If so, minifiers could learn to minify it down to the escape code.
- 2 more replies
New conversation -
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.