On Wednesday, 9 July 2014 at 19:47:02 UTC, Walter Bright wrote:
Yes, I mean transitive, and understand what that implies.
I am positively shocked :)
I have started work on porting the CDGC to D2, have compilable
version (that was
easy thanks to earlier Sean work) but updating implementation
to match new
druntime and pass tests will take quite some time.
Is CDGC's Luca's earlier work on concurrent GC?
Yes.
I'd state it differently: "Marketing fuss about goroutines is
the killer feature
of Go" :) It does not have any fundamental advantage over
existing actor model
and I doubt it will matter _that_ much.
Much of the froth about Go is dismissed by serious developers,
but they nailed the goroutine thing. It's Go's killer feature.
Who are "they"? I don't know any serious developer who praises
goroutines if he was not a CSP fan before. I forsee that it will
make no impact for D because we simply don't have resources to
advertise it as killing feature (on a same scale Go did).
Well, of course, if someone wants to waste his time on this - no
objections from my side :)
I don't know where it comes from but non-nullable reference
type has ZERO value
if it is not the default one.
Making it the default is impossible for D. However,
class _C { ... }
alias NotNull!_C C;
is entirely practical. It's not unlike the common C practice:
typedef struct S { ... } S;
to bring S out of the tag name space.
You are totally missing the point if you consider this even
comparable replacement. Reason why non-nullable types are awesome
because you are 100% sure compiler will force you to handle null
cases and if program compiles it is guaranteed to be safe in that
regard. What you propose makes hardly any difference.
