Skip to content

specify @trusted functions must have @safe interface #3076

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dlang-bot merged 1 commit into from
Mar 3, 2022
Merged

specify @trusted functions must have @safe interface #3076

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion spec/memory-safe-d.dd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).)
Expand Down