destroy and @safe

[Antonio]

On Tuesday, 21 June 2022 at 16:20:32 UTC, Antonio wrote:


> My code starts to be a @safe/@trusted mess (because external 
> libraries). The only solution I have is to "wrap" them or to 
> trust all code by default (I'm using vibe.d that forces @safe 
> code)
>
> Only as a comment: I can remember now when dart/flutter 
> incorporated "sound null safety" and most of the third-party 
> libraries where ported by authors... everybody assumed this 
> will be the way of.   D @safe "optional" adoption is a problem
>
> As a personal advice, I would change the scoring system of the 
> packages to penalize when they are not "safe"

Reading this I realize that the tone is out of place (especially 
because of the great disinterested effort behind the code of 
these libraries and the level of example they provide to those of 
us who are interested in the language).

My apologies.