"Jonathan M Davis" <jmdavisp...@gmx.com> wrote in message news:mailman.659.1327175391.16222.digitalmars-d-le...@puremagic.com... > It's partially available. It just isn't fully implemented, and I don't > know > what's missing from it. And I have no idea when it will be fully > implemented. > You can certainly use it now, but I don't know how much you can really > mark as > @safe at this point, and I don't know how accurate the compiler is in > determining what's @safe beyond the simple restriction that it can't call > functions which aren't @trusted or @safe. > > - Jonathan M Davis
Most of it was implemented last year. There are still plenty of bugs but the majority of it is working. List of things that have been disabled in @safe in the last 7 months or so: - Unsafe pointer arithmetic - Unsafe casting of pointers - Unsafe unions - Catching errors - Casting to/from immutable/shared/const - Taking the address of stack variables - void initializers - Unsafe array casts and probably some others.. It won't give you strong guarantees at this point, but it will catch lots of unsafe stuff.
