From 6f81fb8f1de28270e70a1ffa03a85f7577991b9f Mon Sep 17 00:00:00 2001 From: Walter Bright Date: Mon, 26 Jul 2021 11:00:47 -0700 Subject: [PATCH] specify @trusted functions must have @safe interface --- spec/memory-safe-d.dd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/memory-safe-d.dd b/spec/memory-safe-d.dd index 52b690e734..2d80c4b233 100644 --- a/spec/memory-safe-d.dd +++ b/spec/memory-safe-d.dd @@ -38,7 +38,7 @@ $(H2 $(LNAME2 usage, Usage)) $(P `@trusted` functions have all the capabilities of `@system` functions but may be called from `@safe` functions. For this reason they should be very limited in the scope of their use. Typical uses of `@trusted` functions include wrapping system calls that take buffer pointer and length arguments separately so that - @safe` functions may call them with arrays.) + `@safe` functions may call them with arrays. `@trusted` functions must have a $(DDSUBLINK spec/function, safe-interfaces, safe interface).) $(P `@safe` functions have a number of restrictions on what they may do and are intended to disallow operations that may cause memory corruption. See $(DDSUBLINK spec/function, safe-functions, `@safe` functions).)