u32/u64 <--> int32/int64: dangerous to allow?

[dannywillems]

The doc says u32 (resp. u64) is mapped to int32 (resp. u64). Is it not dangerous to allow this regarding overflow? Should it be mapped to a non native Caml value like done (though using an indirection) in ocaml-integers?

[zshipko]

Yeah, i think this is a situation where we've chosen to prioritize usability at the expense of some safety. In cases where you are concerned about overflow it makes sense to create a custom type that holds the Rust u64.