https://issues.dlang.org/show_bug.cgi?id=18604
Mathias LANG changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://issues.dlang.org/show_bug.cgi?id=18604
--- Comment #7 from anonymous4 ---
Another possibility is -transition=in flag that will deprecate `in` on demand,
and after people remove usage of `in` storage class from their code, it can
start enforce `scope const` meaning.
--
https://issues.dlang.org/show_bug.cgi?id=18604
Carsten Blüggel changed:
What|Removed |Added
CC||chi...@posteo.net
--
https://issues.dlang.org/show_bug.cgi?id=18604
Jonathan M Davis changed:
What|Removed |Added
CC||issues.dl...@jmdavisprog.co
https://issues.dlang.org/show_bug.cgi?id=18604
--- Comment #5 from anonymous4 ---
If one wants to remove `in` attribute the fix is rather simple 's/in/const/'
--
https://issues.dlang.org/show_bug.cgi?id=18604
--- Comment #4 from anonymous4 ---
Also the reason why safe code receives breakage is because it's invalid, and
there should be no guarantee for invalid code to work.
--
https://issues.dlang.org/show_bug.cgi?id=18604
--- Comment #3 from anonymous4 ---
(In reply to Seb from comment #0)
> `in` currently just means `const`
That antifeature was only sort of done for safe code, whatever you do, system
code shouldn't be affected. Though given how much breakage safe cod
https://issues.dlang.org/show_bug.cgi?id=18604
Adam D. Ruppe changed:
What|Removed |Added
CC||destructiona...@gmail.com
--- Comment #2 fro
https://issues.dlang.org/show_bug.cgi?id=18604
--- Comment #1 from Seb ---
https://github.com/dlang/dmd/pull/8021
--
