I mean for privacy things it makes sense to avoid leaking anything. But I fail to understand where the danger is to have anonymous data that says a user installed “Ubuntu-24.04-wappity-whatever.iso” to “KINGSTON DATA TRAVELER 32GB” at some point.

Thanks for taking the time to explain it. Indeed the new runtime method does not guarantee when the resource will be cleaned, so something like that Drop trait would be quite useful

Not sure if that’s what you are referring to as destructors, but they added a new way to have code run at resource collection in go 1.24