Are @safe unittests actually checked for safety?

0xEAB desisma at
Mon Sep 7 20:33:26 UTC 2020

Are unittests that are marked @safe actually checked for safety?
How comes this unittest is @safe when `dirEntries` appears to be 

Example I:
>  Error: @safe function onlineapp.listdir cannot call @system 
> function std.file.dirEntries

Example II (by adr):

> int* a = cast(int*) 0xdeadbeef;
> also was allowed..
> making me think @safe unittest doesn't actually check the safety

  - Elias

PS: is there a @safe version of `dirEntries`?

More information about the Digitalmars-d-learn mailing list