DIP 1028---Make @safe the Default---Community Review Round 1
Adam D. Ruppe
destructionator at gmail.com
Tue Jan 14 01:20:29 UTC 2020
On Tuesday, 14 January 2020 at 01:03:37 UTC, rikki cattermole
wrote:
> I'm not sure I like the idea that attributes are going down
> scopes like you have suggested. It should be explicit that you
> want that.
In as much as like a "@safe class" (or struct/interface/etc)
makes sense, it would surely make the most sense that a @safe
class is one where all methods are @safe. Ditto on nothrow and
pure.
So the descending into scopes is a consequence of that.
Though you could argue that a @nogc class is a class that cannot
live on the GC heap instead... (i was so happy with @disable
operator new until that got deprecated). But still, the same idea
can apply there too. We just need to define it as such.
But that's the formal reason why these specific attributes would
descend into scopes.
More information about the Digitalmars-d
mailing list