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
warning: floating-point types cannot be used in patterns
--> src/main.rs:384:26
|
384 | Some(0.0) => "u32".to_string(),
| ^^^
|
= note: `#[warn(illegal_floating_point_literal_pattern)]` on by default
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620
Could maybe do this by looking at it pre-deserialization to compare against "0.0". But that is if it is even a sane thing to do. Input welcome.
Note that this is only a problem when coming from go; schemars will emit rust's full int range, and we will handle them if set explicitly.
The text was updated successfully, but these errors were encountered:
Currently the kubernetes schemas only mention support int32 or int64 integer types, but the schemas contain a
minimum: f64
where the minimum is set to0.0
in unsigned cases.We could maybe check for it and turn the signed ints into unsigneds at that point:
but that's illegal in the future:
Could maybe do this by looking at it pre-deserialization to compare against "0.0". But that is if it is even a sane thing to do. Input welcome.
Note that this is only a problem when coming from go;
schemars
will emit rust's full int range, and we will handle them if set explicitly.The text was updated successfully, but these errors were encountered: