Thread overview | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
December 18, 2016 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 Sönke Ludwig <sludwig@outerproduct.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|nobody@puremagic.com |andrei@erdani.com -- |
December 18, 2016 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 b2.temp@gmx.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |b2.temp@gmx.com --- Comment #1 from b2.temp@gmx.com --- We could instead imagine a system based on introspection (discover data that should trigger addRange()) and annotations (trust data for for which addRange() should be called but wont). Depending on the result of the introspection, GC.addRange() would be called automatically. See also: - https://forum.dlang.org/thread/ikcgdppksfvfbdqnsgng@forum.dlang.org - https://forum.dlang.org/thread/iubialncuhahhxsfvbbg@forum.dlang.org - https://forum.dlang.org/post/ficbsdfokvbvslatmomr@forum.dlang.org -- |
December 18, 2016 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 --- Comment #2 from Sönke Ludwig <sludwig@outerproduct.org> --- Yeah, I used to simply `static if (std.traits.hasIndirections!T) GC.addRange(...);` in vibe.d's allocator module. Using annotations instead of controlling this at the call site is an interesting idea, although I can see applications for both approaches. Using @nogc sounds good, too, although if that approach is taken, I'd propose to define @nogc as a UDA in object.d instead of adding a new special trait for detecting its presence. -- |
December 27, 2016 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 --- Comment #3 from greenify <greeenify@gmail.com> --- *** Issue 15790 has been marked as a duplicate of this issue. *** -- |
December 27, 2016 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 greenify <greeenify@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |greeenify@gmail.com --- Comment #4 from greenify <greeenify@gmail.com> --- (I just closed https://issues.dlang.org/show_bug.cgi?id=15790 as a duplicate, but it contains a good example that illustrates this issue) -- |
March 10, 2019 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 Johannes Pfau <johannespfau@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johannespfau@gmail.com -- |
March 08, 2020 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 ag0aep6g <ag0aep6g@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |safe CC| |ag0aep6g@gmail.com -- |
March 21, 2020 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 Basile-z <b2.temp@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|b2.temp@gmx.com | -- |
December 17, 2022 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P3 -- |
December 01 [Issue 16982] std.experimental.allocator.make!T must either call GC.addRange or be marked @system | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=16982 --- Comment #5 from dlangBugzillaToGithub <robert.schadek@posteo.de> --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/phobos/issues/9696 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB -- |
Copyright © 1999-2021 by the D Language Foundation