u48::From<u64> should not be implemented, and so on; missing truncation function (like as)

[ariofrio]

The primitive unsigned integer types only implement Smaller::from(bigger) and Bigger::try_from(smaller). They do not implement Bigger::from(smaller), since that could cause truncation. Instead, as is used to convert without overflow checks and with truncation.

These Uint types should work the same way, to avoid accidentally truncating values. Instead, there should be the following options:

• from(...) - only if the conversion is guaranteed to work
• try_from(...).unwrap() - similar behavior to new() currently, panic on overflow
• from_truncated() - or something like that, for an analogous version of primitive as

(Furthermore, it does not seem to be documented whether the Uint::From implementation truncates or panics on overflow.)

[hecatia-elegua]

related to #36, a problem due to trait bounds

[danlehmann]

#47 provides as_(), which provides to opposite of the from_truncated() that was requested in here

[dzmitry-lahoda]

Hello,
After a lot of tinkering in my fin/tradefi/crypto space. I appears that the only option now to go directly to own NewType patterns for all things.
One of things we need is correctness and hardness of violate correctness.

This crate is awesome, likely best in space.
But we cannot adopt it as long as it has correctness issue violated.