shared array?

[Ola Fosheim Grøstad via Digitalmars-d-learn]

On Monday, 14 September 2015 at 13:56:16 UTC, Laeeth Isharc wrote:
> Personally, when I make a strong claim about something and find 
> that I am wrong (the claim that D needs to scan every pointer), 
> I take a step back and consider my view rather than pressing 
> harder.  It's beautiful to be wrong because through recognition 
> of error, growth.  If recognition.

The claim is correct: you need to follow every pointer that 
through some indirection may lead to a pointer that may point 
into the GC heap. Not doing so will lead to unverified memory 
unsafety.

> Given one was written by one (very smart) student for his PhD 
> thesis, and that as I understand it that formed the basis of 
> Sociomantic's concurrent garbage collector (correct me if I am 
> wrong), and that this is being ported to D2, and whether or not 
> it is released, success will spur others to follow - it strikes

As it has been described, it is fork() based and unsuitable for 
the typical use case.

> provided one understands the situation.  Poking holes at things 
> without taking any positive steps to fix them is understandable 
> for people that haven't a choice about their situation, but in 
> my experience is rarely effective in making the world better.

Glossing over issues that needs attention is not a good idea. It 
wastes other people's time.

I am building my own libraries, also for memory management with 
move semantics etc.