[Issue 401] add more std.gc APIs, e.g. std.gc.allocatedMemory();

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=401

Andrei Alexandrescu and...@erdani.com changed:

   What|Removed |Added

Version|unspecified |D2

--

[Issue 401] add more std.gc APIs, e.g. std.gc.allocatedMemory();

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=401

Andrej Mitrovic andrej.mitrov...@gmail.com changed:

   What|Removed |Added

 CC||andrej.mitrov...@gmail.com

--- Comment #2 from Andrej Mitrovic andrej.mitrov...@gmail.com ---
Is this still being planned to be added? Could it become cumbersome for some GC
implementations to expose such an API (e.g. if it's not a O(1) operation but
something way more expensive)? If so then maybe it's best not to try exposing
such operations.

--

[Issue 401] add more std.gc APIs, e.g. std.gc.allocatedMemory();

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=401

--- Comment #3 from Andrei Alexandrescu and...@erdani.com ---
This looks more like a task than an enhancecement request. @Sean okay to remove
it for now?

--

[Issue 401] add more std.gc APIs, e.g. std.gc.allocatedMemory();

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=401

--- Comment #4 from Sean Kelly s...@invisibleduck.org ---
Please do.

--

[Issue 401] add more std.gc APIs, e.g. std.gc.allocatedMemory();

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=401

Andrei Alexandrescu and...@erdani.com changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |LATER

--