Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failure on stable with non-default features #234

Closed
neoeinstein opened this issue Jan 4, 2021 · 2 comments · Fixed by #235
Closed

Build failure on stable with non-default features #234

neoeinstein opened this issue Jan 4, 2021 · 2 comments · Fixed by #235

Comments

@neoeinstein
Copy link

FYI, looks like the issue with #224 has arisen on stable. uom fails to compile on the latest stable version: 1.49.0, with default-features = false and the following options: ["f64", "std", "si", "use_serde"]. I did confirm that going back to the default feature set and just adding "use_serde" works on 1.49.0, however.

Sample of the error listing:

   ::: /Users/me/.cargo/registry/src/github.jparrowsec.cn-1ecc6299db9ec823/uom-0.30.0/src/system.rs:244:20
    |
244 |           pub struct Quantity<D, U, V>
    |                      -------- required by a bound in this
245 |           where
246 |               D: Dimension + ?Sized,
    |                  --------- required by this bound in `si::Quantity`
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider further restricting type parameter `N`
    |
290 |                 V: crate::num_traits::Num + crate::Conversion<V>, N: Integer
    |                                                                 ^^^^^^^^^^^^

error[E0277]: the trait bound `J: Integer` is not satisfied
@iliekturtles
Copy link
Owner

Thanks for the report! I can reproduce and will find a fix. I'm planning to release a new version to crates.io once this is fixed.

@iliekturtles
Copy link
Owner

Thanks again for the report. The fix was just published to crates.io in v0.31.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants