Closed nicolo-ribaudo closed 1 year ago
The “set operations” would be useful. I‘m pretty sure the second never will be, though, because ...
— the illusion that non-ASCII is matchable is limited to literal input: it converts non-ASCII input to percent encoded UTF-8, but regexp pattern components aren’t likewise “translated”, so expressing things like \p{RGI_Emoji_Sequence}
seems to always require input that’s similar to what transpilers might produce today for engines that don’t support multi- or single- codepoint properties at all.
The
v
flags add more support to regular expression features:[[a-z]--[dhk]]
to express "the seta-z
, excluding the setdhk
(https://github.com/tc39/proposal-regexp-v-flag)\p
, such as\p{RGI_Emoji_ZWJ_Sequence}
(https://github.com/tc39/proposal-regexp-unicode-sequence-properties)The HTML
<input>
'spattern
attribute has also been recently updated to usev
instead ofu
(https://html.spec.whatwg.org/#compiled-pattern-regular-expression).