3 ms·
Has anyone suggested adding unsafe type bitmask? E.g. "This code and its transitive dependencies has been carefully validated to be correct", "I had to do this
by nullc 6y ago
Has anyone suggested adding unsafe type bitmask?
E.g. "This code and its transitive dependencies has been carefully validated to be correct", "I had to do this to make it compile", and "This is a FFI that is inherently potentially unsafe".
Then the unsafty of any function would be defined as the logical OR of it and its dependencies... and you could filter what you're willing to use -- maybe with exceptions programmed for specific unsafe blocks, so you could e.g. except specific FFI interfaces without taking random ones people sneak in while they're adding malware to deep dependencies in crates.io to get silently embedded into your software.