-
Notifications
You must be signed in to change notification settings - Fork 198
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 errors in my crates (possibly due to 2018 edition?) #231
Comments
Update: The issue still exists, but I've worked around it for now by going back to the 2015 edition. |
Yes, the rustdoc compiler version is 1.28. I think it is in stable channel, which miss rust 2018 support for the time being. Any idea how to force nightly rustc in docs.rs like 1.30? |
It would be good to see this working. 2018 is awesome and I want to use it with rustdoc |
Looks like its using a nightly, but its pinned to nightly-2018-06-03, prior to any edition support: |
Actually, its stranger than that. Recent docs.rs failures include a log showing the following versions. https://docs.rs/crate/futures-preview/0.3.0-alpha.8/builds/121935
Where the rustc sha matches the merge: onur/rust@b9bf4f162. So rustc 1.28.0-nightly (4ecf12bf0 2018-06-02) is a close approximation which can still be installed with rustup (e.g. |
Since #243 has been merged, docs.rs is using a version of Cargo that can use the |
Seems like this can be closed then, right? |
Looks like it! |
I'm getting build errors for a collection of crates a recently published. The errors seem to imply that doc.rs does not pick up the cargo feature for the 2018 Rust edition yet.
Is this an not-yet-implemented bug of doc.rs, or is this considered functionality that will not be supported until its stable?
The text was updated successfully, but these errors were encountered: