Windows experience is atrocious

[Kagamin]

On Tuesday, 25 July 2023 at 10:21:30 UTC, Paolo Invernizzi wrote:
> We have much more difficulties in reading some "modern" D code, 
> full of scope/ref/in/const/auto ... plus @live ... plus care if 
> scope is before or after, plus yes here scope is doing nothing, 
> etc etc. Maybe because we use python a lot also (you know, 
> machine learning ....) but simplicity, and "explicit is better 
> than implicit" is a value.
>
> I understand your point, but to me the need to explain a 
> programmer, "yes dude, 'in ref' was an ancient way of doing 
> 'in', just keep ALSO that in mind" is a strategic error. 
> Stepping back from the current deprecation mechanics is a pity.

`in ref` is not an ancient way of doing `in`, it's a 
straightforward combination of `in` and `ref`. `-preview=in` 
improves `in`, your code that uses `in` is improved, that's all, 
there's no reason why it should affect `ref`.