If Java with all it that time and money can not create a
performant GC, what hope has D?
Full program tracing GC is a dead horse, it does not scale, all
of the better Java GC's require 2x or memory of the working set
to actually get any speed
isolated task or allocator based memory that
My list is the same as Manu.
For me tools are an intrinsic part of the language, D tools
are so bad that I prefer to write CPP to avoid the anger D IDE's
instill in me
/\*#,
web forum is about a week out of date, and mailing lists give me
brain damage...
thx
ur right I never thought of that, I bet all them game devs never
thought of it either, they so dumb. I bet they never tried to
use a GC, what fools! Endless graphs of traced objects, oh yes
oh yes! It only runs when I allocate, oh what a fool I've been,
please castigate me harder!
Adam p
Any system that forces a single way of handling memory as the
only viable method, be it GC( as D currently does), or ARC, is
undesirable to me
Rust seems to have found a very nice model, and even cpp with
value/unique/rc/weak is IMO superior to what D currently offers
On Monday, 3 Febru
please this GC handbook sound good, can u post it? A queue uses
more memory than not a queue? Fuk I did not know, I so dumb. Live
longer more memory used, what///.
Tuesday, 4 February 2014 at 02:33:50 UTC, Adam Wilson wrote:
On Mon, 03 Feb 2014 18:14:36 -0800, Ola Fosheim Grøstad
wrote:
unique is best, should be default, down with GC!!
Tuesday, 4 February 2014 at 14:19:36 UTC, Frank Bauer wrote:
On Tuesday, 4 February 2014 at 13:18:51 UTC, Dicebot wrote:
For me perfect solution would have been to use an allocator
concept as language basis instead and let you chose any
confo
On Tuesday, 4 February 2014 at 22:30:39 UTC, Walter Bright wrote:
On 2/4/2014 4:23 AM, Michel Fortin wrote:
For the rare cases where you actually want both versions to
work,
I think you're making a vast assumption that the case is rare.
When I write utility functions, I want them to work on a
He said *new* library type, so obviously it would not break
existing code since nothing uses it.
Wednesday, 5 February 2014 at 00:07:30 UTC, Adam Wilson wrote:
On Tue, 04 Feb 2014 15:51:35 -0800, Andrei Alexandrescu
wrote:
Consider we add a library slice type called RCSlice!T. It
would hav
