What's happening with the `in` storage class

[Ali Çehreli]

On 06/08/2018 09:55 PM, Walter Bright wrote:
> On 6/8/2018 7:17 PM, Adam D. Ruppe wrote:
>> On Saturday, 9 June 2018 at 02:13:00 UTC, Walter Bright wrote:
>>> But it was never enforced, meaning that suddenly enforcing it is just 
>>> going to break code left and right.
>>
>>
>> It isn't going to break anything. It is going to *correctly diagnose 
>> already broken code*.
> 
> Not unless the caller was relying on it being 'in'.

It's been clear since I've heard first about it that it meant 'scope const'.

Ali