bearophile wrote:
Lars T. Kyllingstad:
The effect of @safe would be to forbid code that leads to undefined
behaviour, not make it well-defined.
Right, but that's not the solution I was looking for, and it's not
going to solve the problems inherited from C. Because if people that
use D want to use unsafe code too, otherwise they use C#/Java. Having
safe modules in D is a good idea, but safe modules can't be a
replacement for efforts to make safer the low level code too.
I'm confused. It appears you want to write unsafe code and yet have it
be guaranteed safe.
Functions tagged with @system are where you should put unsafe code.
