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
Failing to build on latest nightly, but also when using rustup run nightly-2019-10-28 cargo build:
error[E0658]: `cfg(doctest)` is experimental and subject to change
--> /Users/amooren/.cargo/registry/src/github.com-1ecc6299db9ec823/memoffset-0.5.6/src/lib.rs:74:7
|
74 | #[cfg(doctest)]
| ^^^^^^^
|
= note: for more information, see https://github.com/rust-lang/rust/issues/62210
= help: add `#![feature(cfg_doctest)]` to the crate attributes to enable
error[E0658]: `cfg(doctest)` is experimental and subject to change
--> /Users/amooren/.cargo/registry/src/github.com-1ecc6299db9ec823/memoffset-0.5.6/src/lib.rs:77:7
|
77 | #[cfg(doctest)]
| ^^^^^^^
|
= note: for more information, see https://github.com/rust-lang/rust/issues/62210
= help: add `#![feature(cfg_doctest)]` to the crate attributes to enable
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0658`.
error: could not compile `memoffset`.
warning: build failed, waiting for other jobs to finish...
error: build failed
I don't see a branch for https://github.com/Gilnaa/memoffset that would allow me to take 0.2.1 easily. I tried taking crossbeam = "0.4" and was able to avoid memoffset but of course this is too old and breaks other things.
I ended up editing the locale file in memoffset to add #![feature(cfg_doctest)] and build succeeded. Maybe I should close this and reopen in memoffset repo?
I ended up editing the locale file in memoffset to add #![feature(cfg_doctest)] and build succeeded. Maybe I should close this and reopen in memoffset repo?
hi, we have synced the toolchain using in prod.
rustc --version
rustc 1.43.0-nightly (c20d7eecb 2020-03-11)
Failing to build on latest nightly, but also when using
rustup run nightly-2019-10-28 cargo build
:Looks correct to me?
The text was updated successfully, but these errors were encountered: