https://issues.dlang.org/show_bug.cgi?id=14519
Iain Buclaw changed:
What|Removed |Added
Priority|P1 |P4
--
https://issues.dlang.org/show_bug.cgi?id=14519
Vladimir Panteleev changed:
What|Removed |Added
Component|dmd |druntime
--
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #39 from Vladimir Panteleev ---
*** Issue 22473 has been marked as a duplicate of this issue. ***
--
https://issues.dlang.org/show_bug.cgi?id=14519
Walter Bright changed:
What|Removed |Added
See Also||https://issues.dlang.org/sh
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #38 from Martin Nowak ---
(In reply to Vladimir Panteleev from comment #36)
> Question, is there any overhead in actually verifying the validity of UTF-8
> streams, or is all overhead related to error handling (i.e. inability to be
> noth
https://issues.dlang.org/show_bug.cgi?id=14519
Jack Stouffer changed:
What|Removed |Added
CC||j...@jackstouffer.com
--- Comment #37 from J
https://issues.dlang.org/show_bug.cgi?id=14519
Vladimir Panteleev changed:
What|Removed |Added
See Also||https://issues.dlang.org/sh
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #36 from Vladimir Panteleev ---
Question, is there any overhead in actually verifying the validity of UTF-8
streams, or is all overhead related to error handling (i.e. inability to be
nothrow)?
--
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #35 from Jonathan M Davis ---
(In reply to Martin Nowak from comment #32)
> Summary:
>
> We should adopt a new model of unicode validations.
> The current one where every string processing function decodes unicode
> characters and perfor
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #34 from Vladimir Panteleev ---
(In reply to Martin Nowak from comment #31)
> BTW, this is what I already wrote in comment 23. Not sure why you only
> partially quoted my answer to suggest a contradiction.
Err, well, to be fair, you did
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #33 from Sobirari Muhomori ---
Removing autodecoding is good, but this issue is about making autodecode
@nothrow @nogc.
--
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #32 from Martin Nowak ---
Summary:
We should adopt a new model of unicode validations.
The current one where every string processing function decodes unicode
characters and performs validation causes too much overhead.
A better alternati
https://issues.dlang.org/show_bug.cgi?id=14519
--- Comment #31 from Martin Nowak ---
(In reply to Martin Nowak from comment #30)
> Well, b/c they contain delimited binary and ASCII data, you'll have to find
> those delimiters, then validate and cast the ASCII part to a string, and can
> then use
https://issues.dlang.org/show_bug.cgi?id=14519
Martin Nowak changed:
What|Removed |Added
Summary|[Enh] foreach on strings|Get rid of unicode
|should
14 matches
Mail list logo