On Saturday, 7 December 2019 at 15:57:14 UTC, Jonathan M Davis
wrote:
There may have been some tweaks to std.encoding here and there,
but for the most part, it's pretty ancient. Looking at the
history, it's Seb who marked some if it as being a replacement
for std.utf, which is just plain
On Saturday, December 7, 2019 5:23:30 AM MST Joseph Rushton Wakeling via
Digitalmars-d-learn wrote:
> On Saturday, 7 December 2019 at 03:23:00 UTC, Jonathan M Davis
>
> wrote:
> > The module to look at here is std.utf, not std.encoding.
>
> Hmmm, docs may need updating then -- several functions
On Saturday, 7 December 2019 at 03:23:00 UTC, Jonathan M Davis
wrote:
The module to look at here is std.utf, not std.encoding.
Hmmm, docs may need updating then -- several functions in
`std.encoding` explicitly state they are replacements for
`std.utf`. Did you mean `std.uni`?
It is
On Friday, December 6, 2019 9:48:21 AM MST Joseph Rushton Wakeling via
Digitalmars-d-learn wrote:
> Hello folks,
>
> I have a use-case that involves wanting to create a thin struct
> wrapper of underlying string data (the idea is to have a type
> that guarantees that the string has certain
On Friday, 6 December 2019 at 16:48:21 UTC, Joseph Rushton
Wakeling wrote:
Hello folks,
I have a use-case that involves wanting to create a thin struct
wrapper of underlying string data (the idea is to have a type
that guarantees that the string has certain desirable
properties).
The
Hello folks,
I have a use-case that involves wanting to create a thin struct
wrapper of underlying string data (the idea is to have a type
that guarantees that the string has certain desirable properties).
The string is required to be valid UTF-8. The question is what
the most useful API
