On Monday, 31 July 2017 at 14:51:22 UTC, Timon Gehr wrote:
On 31.07.2017 16:15, Shachar Shemesh wrote:
That's fine, but since, according to the logic presented here,
no OS function can ever be @safe,
This is actually not true. Vladimir was just pointing out a
complication of which to be aware. Are you arguing against
applying due diligence when specifying library interfaces?
Indeed. @safe is not a sandbox, there is no need to actually go
to extreme measures to safeguard against potential changes beyond
our control; just something to keep in mind.