Scope Containers

[bitwise]

On Saturday, 9 March 2019 at 16:34:18 UTC, Eugene Wissner wrote:
> On Saturday, 9 March 2019 at 16:14:34 UTC, bitwise wrote:
>> Hi,
>>
>> Does anybody know if there are any container libraries that 
>> make use of scope for iterator/range safety? or is the 
>> implementation of scope even ready for that right now?
>>
>> Thanks
>
> tanya's containers are good candidates for scope/return, since 
> they don't rely on reference counting and GC like Phobos 
> containers. I intend to introduce scope/return ranges soon, 
> because currently using the containers is not very safe.
> But honestly I'm not expecting much from these annotations. 
> Last time I tested "return" with dip25 it could catch only some 
> basic cases, but not more complicated cases where I assign 
> ranges to variables and then use them.

Ok thanks, I'll have a look.

All I really need is scoped return values so ranges/iterators and 
such can't leave the scope of their containers. So even a partial 
implementation would suffice if it was reliable.