On Tuesday, 27 March 2018 at 09:27:07 UTC, Jonathan M Davis wrote:
On Tuesday, March 27, 2018 09:15:43 Boris-Barboris via Now that
DIP 1000 is being implemented, and scope is actually going to
do something for more than just delegates, it was deemed too
dangerous to have in suddenly really mean both scope and const,
because it would potentially break a lot of code. So, in order
to prevent such breakage, in was changed to officially only
mean const instead of const scope.
https://issues.dlang.org/show_bug.cgi?id=17928
- Jonathan M Davis
Well, here I am, writing "in" everywhere in anticipation of DIP1k
)
But I guess "do not break" at this point is indeed more important.
Thanks.
