Bug 11304 – In case of different @safe/@trusted/@system attributes the weaker is selected

In case of different attributes the weaker is selected i.e. `f1` is expected to be @safe: --- void f() @system {} @trusted { void f1() @safe { static assert(!__traits(compiles, f())); } // assert fails } @safe { void f2() @trusted { f(); } // @trusted as expected } // It would be also good to reject g1/g2: @safe void g1() @trusted { f(); } // compiled as @trusted @trusted void g2() @safe { f(); } // compiled as @trusted ---

(In reply to Denis Shelomovskij from comment #0) > void f() @system {} > > @trusted { > void f1() @safe > { static assert(!__traits(compiles, f())); } // assert fails > } From 2.066, f1 is marked as @safe, then the assert failure is fixed. > // It would be also good to reject g1/g2: > @safe void g1() @trusted { f(); } // compiled as @trusted > @trusted void g2() @safe { f(); } // compiled as @trusted From 2.066, those fails to compile with "conflicting storage class" error.