ImportC and nothrow/@nogc?

[Lance Bachmeier]

On Wednesday, 28 August 2024 at 13:41:47 UTC, Manu wrote:

>> The author of the C code likely has no idea that the caller 
>> from D exists
>> let
>> alone that it would require that the C code not call any D 
>> functions.
>>
>
> The author of the library expects you to use the library via 
> the API they
> provide... their API is C code; if C code is nothrow @nogc, 
> then the
> callback you provide is necessarily nothrow and @nogc also.
> I really can't see the fuss here...

Strong agree. While technically Walter is correct, it would 
require doing something that doesn't make a lot of sense, at the 
cost of what started this thread.