D-ark corners - algorithms, ranges, and auto ref - best practices guides.

[aliak]

On Tuesday, 23 July 2019 at 17:17:25 UTC, H. S. Teoh wrote:
> On Tue, Jul 23, 2019 at 01:51:42PM +0000, aliak via 
> Digitalmars-d wrote: [...]
>> With some help from the forums, the essence of the problem was 
>> the following:
>> 
>> 1. algorithm returned by auto ref.
>> 2. the range's front was "ref front() {...}"
> [...]
>
> Isn't this precisely the sort of problem dip25 / dip1000 are 
> supposed to catch?  Are you compiling with -dip25 -dip1000?  
> Are DIP25/DIP1000 (or their current implementations) not 
> catching this particular case for some reason?
>
>
> T

Not compiling with those no.

Is @safe supposed to solve all memory corruption or is it only if 
dip1000 and dip25 is on. So default @safe is not @safe?