On Tuesday, 26 May 2020 at 01:16:49 UTC, Walter Bright wrote:
On 5/24/2020 5:56 PM, Timon Gehr wrote:
It's only greenwashing if it's misleading. Putting @safe is a
lie, putting @trusted is honest.
It is not honest unless the programmer actually carefully
examined the interface and the documentation to determine if it
is a safe interface or not. For example, labeling memcpy() with
@trusted is not honest.
Forcing people to add uncheckable annotations is a path to
convenience, not honesty.
What is the difference of @safe to @trusted in that respect? Does
the compiler "carefully examines" any interface or documentation?
Why not simply introducing new label as a solution, something in
the realm @extern_safe_dont_know?
