[Issue 12941] New: Everything should be @unsafe by default, and explicitly vetted (and documented) as @safe

via Digitalmars-d-bugs digitalmars-d-bugs at puremagic.com
Wed Jun 18 10:18:00 PDT 2014


https://issues.dlang.org/show_bug.cgi?id=12941

          Issue ID: 12941
           Summary: Everything should be @unsafe by default, and
                    explicitly vetted (and documented) as @safe
           Product: D
           Version: D2
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: DMD
          Assignee: nobody at puremagic.com
          Reporter: hsteoh at quickfur.ath.cx

Since everyone keeps talking about this in the NG but nobody does anything
about it, I'll put myself in the firing range and do it.

Basically, the compiler should treat everything as non- at safe, except for a list
of @safe operations that is well-defined and well-documented. For starters,
let's make a list of operations that are known to be @safe on this bug, and
once the list is reasonably complete, we can start looking at the compiler
sources to tweak the current implementation to match this list.

--


More information about the Digitalmars-d-bugs mailing list