On Monday, 22 October 2018 at 00:55:00 UTC, Timon Gehr wrote:
On 22.10.18 02:46, Nicholas Wilson wrote:
On Monday, 22 October 2018 at 00:38:33 UTC, Timon Gehr wrote:
I just did,
Link please?
https://forum.dlang.org/post/pqii8k$11u3$1...@digitalmars.com
That contains no code.
Not all of the parties that participate in the data race are in
@trusted code.
There are two cases of @trusted code, bad and good. Bad trusted
code can indeed be misused by @safe code to corrupt memory. Good
trusted code cannot.
What part of the proposal breaks the type system? The implicit
conversion to shared implies that the passed to function is @safe
iff all the functions it calls are @safe only call function with
that parameter to other shared @safe functions _OR_ they are
@trusted.
The point of @trusted is modularity: you manually check
@trusted code according to some set of restrictions and then
you are sure that there is no memory corruption.
Yes. And?
