You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So in the code(number.rs), when "arbitrary_precision" feature is enabled, this is the Number representation, it seems.
#[cfg(not(feature = "arbitrary_precision"))]#[derive(Copy,Clone)]enumN{PosInt(u64),/// Always less than zero.NegInt(i64),/// Always finite.Float(f64),}
The question is, is it an API level gurantee that running one of:
is_u64()
is_i64()
is_f64()
will return true or is it just the case at the moment?
The text was updated successfully, but these errors were encountered:
So in the code(number.rs), when "arbitrary_precision" feature is enabled, this is the Number representation, it seems.
The question is, is it an API level gurantee that running one of:
is_u64()
is_i64()
is_f64()
will return true or is it just the case at the moment?
The text was updated successfully, but these errors were encountered: