all OS functions should be "nothrow @trusted @nogc"

[Shachar Shemesh via Digitalmars-d]

On 31/07/17 16:33, Vladimir Panteleev wrote:
> On Wednesday, 26 July 2017 at 17:48:21 UTC, Walter Bright wrote:
>> On 7/26/2017 6:29 AM, Kagamin wrote:
>>> Should we still try to mark them safe at all?
>>
>> Marking ones that are safe with @safe is fine. OS APIs pretty much 
>> never change.
> 
> Sometimes operating systems add new flags to their API which change how 
> some values are interpreted. Some API functions may, for example, 
> normally take a pointer to a such-and-such struct, but if a certain flag 
> is specified, the parameter is instead interpreted as a pointer to a 
> different data type. That would be one case where an API call becomes 
> un- at safe due to the addition of a flag.
> 

One of the things that really bother me with the D community is the 
"100% or nothing" approach.

System programming is, by definition, an exercise in juggling 
conflicting aims. The more absolute the language, the less useful it is 
for performing real life tasks.

Shachar