| 07:05 | <ptomato> | I'll take a look, thanks for the heads up! |
| 08:53 | <ptomato> | shu: no problem to change that since it's only used for formatting property names, but as far as I can tell from reading ECMA-262, even implementations without i18n are required to support those properties? |
| 08:55 | <ptomato> | (by "those properties" I mean ID_Start and ID_Continue) |
| 08:58 | <canadahonk> | yeah, wasn't that part of https://github.com/tc39/proposal-regexp-unicode-property-escapes ? |
| 13:34 | <canadahonk> | https://github.com/tc39/test262/pull/3842 for ref btw :) |
| 14:39 | <shu> | ptomato: huh, oh really? let's see |
| 14:51 | <shu> | so i think what's happening is, V8 depends on ICU for those property names, which is pretty reasonable, because that's where those property names are |
| 14:51 | <shu> | and the "no i18n" build is actually the "no ICU dependency" build |
| 14:55 | <shu> | in any case i think i agree with your reading of the spec, but in practice i don't know yet |
| 14:57 | <canadahonk> | it no longer uses those in main now btw |
| 14:57 | <shu> | thank you |
| 15:40 | <Richard Gibson> | I agree with ptomato, and it looks to me like not just /…/u regular expressions but also String.prototype.toLowerCase and toUpperCase depend upon the Unicode Character Database (e.g., "İKÅΩↃΣ".toLowerCase() === "i̇kåωↄς" and "ßⅶςµffև".toUpperCase() === "SSⅦΣΜFFԵՒ" must hold in every implementation). UAX #44 should probably move from Bibliography to Normative References. 🤔 |
| 16:47 | <shu> | we should probably discuss if implementations that actually don't ship Intl (Moddable) still support these features, or if we need to redraw the optionality line for stuff along ICU lines |
| 16:47 | <shu> | the no-i18n build for V8 is mostly not that well supported |
| 16:48 | <shu> | that is, in an ideal world, we'd only have one configuration of V8 that always includes i18n |
| 18:18 | <Richard Gibson> | the version of Moddable XS fetched by esvu at least correctly supports both the above toUpperCase()/toLowerCase() behavior and /…/u regular expressions with \p{<property name>} contents |