Subject: Re: [SG16-Unicode] code_unit_sequence and code_point_sequence
From: Mark Zeren (mzeren_at_[hidden])
Date: 2018-06-19 09:52:33
ï»¿On 6/19/18, 8:40 AM, "unicode-bounces_at_[hidden] on behalf of Lyberta" <unicode-bounces_at_[hidden] on behalf of lyberta_at_[hidden]> wrote:
Remember there are tons of code unit sequence types out there:
std::basic_string, Microsoft's CString, Qt's QString, wxWidgets's
wxString. We want to support all those types if people provide their
encoding form traits.
[mjz] This is one approach. Another is Zach's opinionated "there is only one storage container" approach. We don't know which way the committee will go until we bring proposals to a meeting.
My use case, where I want encoding (I'm less sure about form) represented in the type system is satisfied by both approaches -- as long as the opinionated approach chooses UTF-8.
SG16 list run by firstname.lastname@example.org