Robin Leroy

I addressed the comments I had made above, moving the LB15a-specific logic into the state table (it is not exactly pretty, we should probably invest in some extensions to the...

> I should probably try 2 000 000 as I did in https://github.com/unicode-org/icu4x/pull/4389. ``` fatal error: rustc does not support files larger than 4GB ```` Maybe we should be using...

Now tested with 2 000 000 random strings. Before ICU 76 (specifically, before https://github.com/unicode-org/icu/pull/3028) it doesn’t make sense to go further than that, since it turned out the PRNG was...

It is a sensible idea to provide something to help with planning burns for vessels without attitude control (for which the burn definition lives in a two-dimensional space, with, _e.g._,...

> however, shouldn't we have such data precalculated? We have the IndexUnicodeProperties data precalculated, but probably not the ToolUnicodeProperties data which lurks in the darker and more ancient corners of...

There are two main implementations of UCD parsing and data structures for accessing the UCD in here: * org.unicode.text.UCD, vintage 1996, which has ToolUnicodeProperties built on top of it; *...

> But again, shouldn't we pre-create the content in Generated rather than have it created on the fly in each Cloud Run instantiation? In principle, sure, in practice, it’s not...

The approach taken in this hack also prevents us from accessing the history of property assignments in dot-dot releases, which had a different UCD but no new characters and no...

At a very quick glance I think this looks good. This week I am participating in ISO/IEC JTC 1/SC 2 and ISO/IEC JTC 1/SC 2/WG 2, and I will be...

> Should we differentiate between properties and data Extremely yes. I am trying to sort out this mess in https://github.com/unicode-org/unicodetools/pull/1064, and in the process I found https://github.com/unicode-org/properties/issues/390. > does it...