Make @safe the default

[WalterBright]

No description provided.

[JinShil]

FYI, @WalterBright, I had already started a DIP for this at #153. It's far more elaborate and you may want to take something from it (or not). I'd rather have you take the lead, so I closed mine.

[JinShil]

I was thinking about adding a -transition=explicitSafety to identify any places in one's code that doesn't have @safe, @system, or @trusted explicitly specified. I think that would help users find where they need to add attribution to make their code resistent to breakage.

[dkorpel]

I'd rather have you take the lead, so I closed mine.

I understand, but it's a pity the extensive DIP gets closed in favor of the bare bones one.
I hope Walter takes lots of inspiration from it.

Also I hope that DIP1000 and successors are sorted out before this kicks in, because currently @safe is the one D attribute I sort of gave up on for now because it's a mess.
There's little value in boasting @safe by default when it doesn't work yet.
There's not a single example of a working manually managed @safe container out there.
See e.g. automem issues 25, 26, 29, 29.

[p0nce]

Is there any commercial D user that actually asked for that?

[JesseKPhillips]

I like the transition flag but I think a version road map would be good. We would keep transition, but decide groupings of breaking changes.

D 3 should be safe by default and no auto decoding. Yes understand this can create some duplicate efforts, but may help communicate the plan for what D should look like.

https://forum.dlang.org/post/bfgpindcvbjmxscsgudh@forum.dlang.org

[WalterBright]

because it's a mess

Please add specific issues to bugzilla, and tag with the safe keyword. Issues not put in bugzilla will not get fixed.