dsimcha: > The exception, though, is when someone is using a construct that would only be > used by people who really need efficiency, and thus has already explicitly > asked > for efficiency. This includes parallel foreach. In these cases, I think that > "efficiency first, safety second" has to be the rule and there should never, > ever > be any implicit copying. If you can't implement this safely, then it should > be > implemented unsafely and place the onus of ensuring safety on the programmer.
@system parallel_foreach() Vs: parallel_foreach() ? :-) When they can be created it's useful to have handy safe alternatives (possibly the default ones). Bye, bearophile
