[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #15 from github-bugzi...@puremagic.com --- Commits pushed to dmd-cxx at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/187e2b769b7ab1e2509d54e31cddc007b423fc8a fix issue 13348 https://github.com/dlang/phobos/commi

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #14 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/187e2b769b7ab1e2509d54e31cddc007b423fc8a fix issue 13348 https://github.com/dlang/phobos/commit

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #13 from github-bugzi...@puremagic.com --- Commits pushed to stable at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/187e2b769b7ab1e2509d54e31cddc007b423fc8a fix issue 13348 https://github.com/dlang/phobos/commit

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #12 from Steven Schveighoffer --- (In reply to Dmitry Olshansky from comment #11) > > At this point, if we were to fix purity, I think this is the way to go. > > From your comments in the code, you said that most of the time allocations

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #11 from Dmitry Olshansky --- > At this point, if we were to fix purity, I think this is the way to go. From > your comments in the code, you said that most of the time allocations will > not happen. I'm sure this varies with the langua

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 greensunn...@gmail.com changed: What|Removed |Added CC||greensunn...@gmail.com --- Comment #

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #9 from Steven Schveighoffer --- (In reply to Dmitry Olshansky from comment #7) > Should I just use GC? At this point, if we were to fix purity, I think this is the way to go. From your comments in the code, you said that most of the tim

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #8 from hst...@quickfur.ath.cx --- Here's a thought, I don't know how feasible it is, but what about using slices of the input string, and decode on demand? Of course, this doesn't work for general input ranges (have to allocate somehow in

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 --- Comment #7 from Dmitry Olshansky --- > OK, so pretty much all the problems stem from malloc/realloc/free being used > to manage the memory of the Grapheme type. Should I just use GC? --

[Issue 13348] std.uni.Grapheme is impure due to using C malloc and friends

https://issues.dlang.org/show_bug.cgi?id=13348 Steven Schveighoffer changed: What|Removed |Added CC||dmitry.o...@gmail.com Summ