I disagree. `@safe` is one thing, `@trusted` is another.

Take for instance `core.stdc.stdlib.abs()`. The C specification tells us enough to know that this function -- in a sane, conforming implementation -- will behave safely. We don't know the source code, so quite obviously `@safe` is inappropriate. But `@trusted` makes exactly *perfect* sense here: We trust that the implementation follows the specification and is safe. It is exactly what we use `@trusted` for in normal D code.