DIP1000 scope inference

[Nick Treleaven]

On Wednesday, 26 October 2022 at 08:37:36 UTC, rikki cattermole 
wrote:
> On 26/10/2022 9:03 PM, Walter Bright wrote:
>> A very good question. Clearly, having code work when it is 
>> @safe, but cause memory corruption when it is marked @trusted, 
>> is the wrong solution. This should never happen. I'm not sure 
>> what the solution should be here.
>
> At the very least, if no solution can be determined this needs 
> to be reverted before 2.101.0.

There's nothing to revert that corrupts memory (without 
incorrectly writing scope), see Paul's reply.