Steven Schveighoffer has contributed an article to the blog explaining @trusted and advising on its proper usage.

Post: https://dlang.org/blog/2016/09/28/how-to-write-trusted-code-in-d/

Reddit: https://www.reddit.com/r/programming/comments/54wg8r/memory_safety_how_to_write_trusted_code_in_d/

On Wednesday, 28 September 2016 at 14:02:45 UTC, Mike Parker wrote:
> Steven Schveighoffer has contributed an article to the blog explaining @trusted and advising on its proper usage.
>
> Post: https://dlang.org/blog/2016/09/28/how-to-write-trusted-code-in-d/
>
> Reddit: https://www.reddit.com/r/programming/comments/54wg8r/memory_safety_how_to_write_trusted_code_in_d/

There is a typo in
ssize_t read(int fd, void *ptr, size_t nBytes);

On Wednesday, 28 September 2016 at 14:34:20 UTC, jmh530 wrote:
> On Wednesday, 28 September 2016 at 14:02:45 UTC, Mike Parker wrote:
>> Steven Schveighoffer has contributed an article to the blog explaining @trusted and advising on its proper usage.
>>
>> Post: https://dlang.org/blog/2016/09/28/how-to-write-trusted-code-in-d/
>>
>> Reddit: https://www.reddit.com/r/programming/comments/54wg8r/memory_safety_how_to_write_trusted_code_in_d/
>
> There is a typo in
> ssize_t read(int fd, void *ptr, size_t nBytes);

Are you referring to ssize_t? If so, that's not a typo. It's the signed version of size_t. The * should be next to the void, though.

On Wednesday, 28 September 2016 at 14:44:17 UTC, Mike Parker wrote:
>
> Are you referring to ssize_t? If so, that's not a typo. It's the signed version of size_t. The * should be next to the void, though.

I thought you meant size_t, but glad to know that I wasn't totally wrong.