[Apologies for my previous incomplete email - please ignore it.] This raises an interesting question:
> 3) Remove 'param parSafe' from methods on RandomStream I suspect that there will be other cases like this. I.e. an interface to be documented has a feature that is unused, as far as we can tell, or perhaps used infrequently. And, this feature adds substantial bulk to documentation. My preference is to avoid dropping such a feature just because it presents a documentation issue. > 1) Parameterize RandomStreams by 'type eltType' > [...] I agree it will make common uses easier/consistent. However, what if I need to randomize several arrays of different element types? This proposal will force me to create several RandomStreams, and I will have to go through the hassle of ensuring that their random sequences do not overlap. I propose that we support such a scenario as well, one way or another. Vass ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
