DIP1028 - Rationale for accepting as is
Zoadian
no at no.no
Mon May 25 12:22:25 UTC 2020
On Monday, 25 May 2020 at 11:40:46 UTC, Johannes T wrote:
> On Monday, 25 May 2020 at 10:19:22 UTC, Johannes Loher wrote:
>> [..]
>> But with the DIP in its current form, we make @safe lose its
>> meaning and power, which is much worse in my opinion.
>> [..]
>
> The alternative, not making extern @safe, would result in more
> untrustworthy @trusted code we have to worry about. It's a
> vicious circle.
> I try to relax my view on extern annotations. They are @system.
> We *should* go ahead and diligently mark with @trusted. From
> experience, it doesn't normally happen.
> I don't like @safe extern, but it seems like the lesser evil.
> Walter got a lot of flak. I tried to retrace his thoughts and
> see the merits.
there is no such thing as a trustworthy @trusted. not with how
the whole safety system work now.
you can break previously verified @trusted code by just writing
@safe code today.
More information about the Digitalmars-d-announce
mailing list