December 09, 2020
On Wednesday, 9 December 2020 at 21:21:52 UTC, Paul Backus wrote:
>
> The meanings of @safe and @trusted are spelled out in the language spec. [1] They are not a matter of opinion.
>
> [1] https://dlang.org/spec/function.html#function-safety

It seems so. So the greenwashing approach for partial `@safe`ty is not currently officially supported. I'll have to remember that.

It can still be debated whether it should be, through.


> @safe does not find bugs; it prevents them.

Ah, that's better wording. It isn't really a bug if it does not pass compilation.
December 09, 2020
On Wednesday, 9 December 2020 at 21:49:54 UTC, Dukc wrote:
> On Wednesday, 9 December 2020 at 21:21:52 UTC, Paul Backus wrote:
>> @safe does not find bugs; it prevents them.
>
> Ah, that's better wording. It isn't really a bug if it does not pass compilation.

Well, also, the things that @safe flags are not actually bugs, but rather things that could *potentially* lead to bugs somewhere down the line. It is entirely possible to write code that has no memory-safety bugs, but is also not @safe.
1 2 3 4 5 6 7 8
Next ›   Last »