Do we really need @unsafe?

[Walter Bright]

@unsafe was suggested (I think by Don) to provide symmetry with @safe 
and @trusted. This is a good point, but I'm starting to think that 
@unsafe is not a good idea.

For example, one could make an entire module safe with:

-------------------
module foo;
@safe:
[...]
-------------------

And an observer could conclude that foo only contains safe and trusted 
code. But if @unsafe could override, he has to delve into it looking for 
@unsafe as well.

Furthermore, why would a safe module wish to expose unsafe functions? 
Shouldn't the programmer instead be obliged to produce trusted functions 
in it?