In a sense, a SharedArray should act like an Array if you're using a single core. I'm not saying all methods have been implemented for them, but if the code runs then it certainly shouldn't give different answers. So I'd say this is a bug.
So now that we know it's a bug, I'd urge you to file an issue. The advantage is that it's less likely to be forgotten than an email. If whoever digs into it (maybe me but not this week, maybe someone else) discovers there isn't really a problem after all, you can blame me :-). --Tim On Wednesday, April 08, 2015 08:15:38 AM Nils Gudat wrote: > Apologies again for being a little slow (mentally now, not in terms of > response time); by trying an Array you mean running the code in single-core > mode and using an Array instead of a SharedArray? Running it in parallel > with a regular Array (unsurprisingly) doesn't work. So I have: > > Single core: initializing result* as Arrays works, initializing as > SharedArrays gives unexpected result > Multi-core: initializing result* as Arrays returns empty Arrays, > initializing as SharedArrays works > > I'm still not sure whether this is a bug or the "intended" behaviour of > SharedArrays, i.e. whether SharedArrays maybe just aren't meant to work in > this situation when not using multiple processes. I'm a bit reluctant to > file an issue simply because my understanding of the workings of > SharedArray is limited, so I thought I'd ask for help here first.
