An application would have many (maybe as many as10,000) threads. Each thread would be truly thread safe, not this current "copy-on-create" crap that Perl5 has. Real separate code in each thread. The backbone of each thread would be a vector that you can grow/shrink by adding/subtracting elements.....it's the old "i,j,k,l,m,n" thing in vector spaces.

Each vector element is only readable by every other thread-object in thread:shared space. The space elements being added/subtracted are orthoganal....even to the higher dimensions.

Wait, did I just try to reinvent PDL ? No, because the key is the independent threads containing a self-looping object(eek! they're alive :-) ). This is probably better done in C, with the libglib of gtk+.

So I guess I'm asking is Perl6 going to be cleaner on threads, without the copy-on-write spawning. Truly independent threads.