Well, merely warning won't disable the feature. You could `forbid` these lints, and then require clippy for CI or something, the same way many people require un

Well, merely warning won't disable the feature. You could `forbid` these lints, and then require clippy for CI or something, the same way many people require unit tests pass in CI. I'd be very surprised if you find all three problematic. The problems you described feel like shadow_unrelated You are absolutely right that anyhow doesn't do what you want for a no-alloc situation like a kernel driver or some ESP32 firmware - however it won't compile without an allocator, so, seems like you'd be shifting that problem hard left, the programmer who adds anyhow to their no allocator firmware can't build it. Yes, I see now what Zig has here is literally a syntax check and so Rice doesn't apply because in Zig the function which returns an error is syntactically different and so Zig can say hey, this is an error function and those are different. I prefer the situation in Rust, but this is an important difference albeit one I don't agree with.