RFC: naming for FrontTransversal and Transversal ranges

[Andrei Alexandrescu]

Denis Koroskin wrote:
>> You can reuse memory even if it comprehends more complex patterns
>> than one single allocation.
>> 
>> Andrei
> 
> I *highly* doubt it is worth the trouble. Most likely, this container
> won't be lock-free and scalable anymore. Performance will also
> degrade dramatically.

How did you get to "most likely"? There's so many factors in the 
equation. What is the alternative? Why wouldn't the code be lock-free? 
Why would it not be scalable?

> Besides, the more I think about thread-local/shared separation that
> is going to come to D2, the more I see that there is absolutely no
> need to make Phobos containers thread-safe. Most containers will be
> thread-local and won't need any synchronization at all.

I agree. But you also don't want to preclude using a shared container 
either.


Andrei