[SG16-Unicode] code_unit_sequence and code_point_sequence
Lyberta
lyberta at lyberta.net
Tue Jun 19 15:03:00 CEST 2018
Martinho Fernandes:
> As you said, there are many types out there that would support this
> concept, some of them already in the standard library. Why do I need a
> new one, and why would I use it instead of any of the other ones?
Because deducing std::basic_string as a code unit sequence for string
literals would be bringing an irrelevant broken legacy things such as
std::char_traits into otherwise extremely clean design.
I really really want C++ to show all other languages how proper Unicode
handling should be done. code_point_sequence<std::basic_string<...>>
would work absolutely fine for legacy codebases that can't migrate away
from std::basic_string. code_point_sequence_view<std::basic_string<...>>
would have no overhead too.
I've heard that there is work on a new allocator design too so having
std::allocator<std::byte> as default allocator is just a placeholder.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
Url : http://www.open-std.org/pipermail/unicode/attachments/20180619/89c7f4a8/attachment.bin
More information about the Unicode
mailing list