Date: Wed, 17 Mar 2021 16:09:29 -0400
On 3/17/21 10:45 AM, Steve Downey via SG16 wrote:
>
>
> On Wed, Mar 17, 2021 at 9:22 AM Tom Honermann via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> On 3/17/21 5:23 AM, Corentin Jabot wrote:
>>
>>
>> On Tue, Mar 16, 2021 at 3:59 PM Tom Honermann via SG16
>> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>>
>> * P1628 <https://wg21.link/p1628>: Unicode character properties
>>
>> As the author I do not expect to do further work on this in the
>> 23 cycle
> That matches my expectations, thanks for confirming.
>
> Not that we have a paper, or that I'm asking for anyone to do work,
> but without access to the UCD, all the other algorithms are off
> the table. In theory it's an implementation detail, in practice it
> would be an ABI break to change the APIs for property lookup, and
> having two or more mechanisms in a std library implementation seems
> like a bad idea.
> Expectation setting is important. It's not clear to everyone how the
> Unicode layers work, even if the explanations are straight-forward.
We don't have proposals for any algorithms yet. I would feel some
concern about trying to standardize access to the UCD without algorithms
to go with it; at least reference implementations showing what is possible.
Perhaps something that might be helpful is an audit of the algorithms
and which UCD properties they each depend on. That might help to
prioritize which UCD properties to expose first, which ones we can
guarantee stability for, etc...
Tom.
>
>
> On Wed, Mar 17, 2021 at 9:22 AM Tom Honermann via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> On 3/17/21 5:23 AM, Corentin Jabot wrote:
>>
>>
>> On Tue, Mar 16, 2021 at 3:59 PM Tom Honermann via SG16
>> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>>
>> * P1628 <https://wg21.link/p1628>: Unicode character properties
>>
>> As the author I do not expect to do further work on this in the
>> 23 cycle
> That matches my expectations, thanks for confirming.
>
> Not that we have a paper, or that I'm asking for anyone to do work,
> but without access to the UCD, all the other algorithms are off
> the table. In theory it's an implementation detail, in practice it
> would be an ABI break to change the APIs for property lookup, and
> having two or more mechanisms in a std library implementation seems
> like a bad idea.
> Expectation setting is important. It's not clear to everyone how the
> Unicode layers work, even if the explanations are straight-forward.
We don't have proposals for any algorithms yet. I would feel some
concern about trying to standardize access to the UCD without algorithms
to go with it; at least reference implementations showing what is possible.
Perhaps something that might be helpful is an audit of the algorithms
and which UCD properties they each depend on. That might help to
prioritize which UCD properties to expose first, which ones we can
guarantee stability for, etc...
Tom.
Received on 2021-03-17 15:09:32