Re: Bug w/tuple of custom types?

On Mon, 21 Mar 2011 13:03:25 -0400, Magnus Lie Hetland mag...@hetland.org wrote: Sample program: import std.typecons; typedef uint oid_t; void main() { Tuple!(uint,uint) key; // Tuple!(oid_t,oid_t) key; // Doesn't work } If I use the last tuple instead of the first, I get the

Re: Bug? GC collects memory that references itself.

Jeremie Pelletier jerem...@gmail.com wrote: I need objects that may live without any references in GC memory, this is for bindings to a C++ library. Using ranges or roots would be very inneficient so my solution was to have the objects reference themselves until the C++ side of the object

Re: Bug? GC collects memory that references itself.

Jeremie Pelletier Wrote: If its a feature of the GC to prevent objects from never being collected, how do I bypass it? Implement IUnknown?

Re: Bug? GC collects memory that references itself.

Simen Kjaeraas wrote: Jeremie Pelletier jerem...@gmail.com wrote: I need objects that may live without any references in GC memory, this is for bindings to a C++ library. Using ranges or roots would be very inneficient so my solution was to have the objects reference themselves until the C++

<    1   2   3   4   5