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
The inclusion of the edition = "2018" line in the Cargo.toml manifest is causing builds to fail on rustc 1.30.0. Attempting to use claim on this compiler version results in the following error:
Compiling claim v0.4.0
error: Edition 2018 is unstable and only available for nightly builds of rustc.
error: Could not compile `claim`.
The solution is to drop the edition tag completely. That seems to be best, since it isn't really a 2018 edition crate anyways, if you're targeting and testing against compiler versions from before 2018.
A similar problem is that the crate doesn't build on anything before rustc 1.6.0, despite your version compatibility badge claiming support all the way to 1.0.0. This is because of the use of #![no_std], which wasn't stable before 1.6.0. This can be resolved using autocfg, similar to what I've done in similar situations. The error message when building on rustc 1.0.0 supports this:
claim-0.4.0/src/lib.rs:1:1: 1:11 error: no_std is experimental
claim-0.4.0/src/lib.rs:1 #![no_std]
^~~~~~~~~~
I can put together a PR with my suggested fixes for these issues.
The text was updated successfully, but these errors were encountered:
The inclusion of the
edition = "2018"
line in theCargo.toml
manifest is causing builds to fail onrustc 1.30.0
. Attempting to useclaim
on this compiler version results in the following error:The solution is to drop the
edition
tag completely. That seems to be best, since it isn't really a 2018 edition crate anyways, if you're targeting and testing against compiler versions from before 2018.A similar problem is that the crate doesn't build on anything before
rustc 1.6.0
, despite your version compatibility badge claiming support all the way to1.0.0
. This is because of the use of#![no_std]
, which wasn't stable before1.6.0
. This can be resolved usingautocfg
, similar to what I've done in similar situations. The error message when building onrustc 1.0.0
supports this:I can put together a PR with my suggested fixes for these issues.
The text was updated successfully, but these errors were encountered: