I'd rather have explicit seperation of concern for UB-causing behavior than have a generic monad approach. Perhaps the examples I've seen in Rust just don't do

I'd rather have explicit seperation of concern for UB-causing behavior than have a generic monad approach. Perhaps the examples I've seen in Rust just don't do that, because part of the appeal of Rust is that you sort of don't have to. That makes the cognitive load acceptable and documents all the UB prevention in source code. It's a habit arrived at from using formal instantiation protocols that were driven from external to the device being made - starting with RFC1695.