Re: `in` no longer same as `const ref`

[Adam D. Ruppe via Digitalmars-d]

On Monday, 30 January 2017 at 00:26:27 UTC, Walter Bright wrote:
I was afraid that by checking it, too much code would break.

Code that was using it improperly was *already* broken. Now, the 
compiler will simply tell them, at compile time, why instead of 
letting it silently accept undefined behavior.