-
Notifications
You must be signed in to change notification settings - Fork 208
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
Add option to build with stable #506
Comments
This is not a docs.rs bug. Feel free to open an issue in https://github.com/rust-lang/rust/ if you think it is sufficiently different from rust-lang/rust#67006. |
It is a build failure that would be fixed by building this crate with rustdoc stable,which is why I mention it at the end of the comment. |
|
This seems unlikely to be possible in the near future, see #228 (comment). However I would like to support this so I'm leaving the issue open. |
The nightly options are |
@rodrimati1992 I rebuilt your crate manually, but it failed with a different ICE! Sorry for the trouble haha, here's the new error if you want to file a bug: https://docs.rs/crate/abi_stable/0.8.1/builds/208296 |
This ICE has already been reported for servo in rust-lang/rust#67601 . |
We also now see failure to build due to rust-lang/rust#84738. Maybe its time to switch to stable (or stable-built-with-unstable-flags-enabled) now given the recent instability of nightly? |
@TheBlueMatt this is not currently possible, see #506 (comment) |
Correct me if I’m wrong, but that doesn’t seem to preclude the possibility of pinning nightly instead of upgrading regularly? If nightly were pinned and only updated more occasionally we could avoid some of the breakage, no?
… On Jun 14, 2021, at 16:20, Joshua Nelson ***@***.***> wrote:
@TheBlueMatt this is not currently possible, see #506 (comment)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Pinning a nightly is tracked by #228, not here. I am not willing to have the docs.rs team be in charge of finding a "blessed" nightly that works for everyone, we don't have the time or manpower to be responsible for that. |
Is it not possible to build the release tags without the release bit set - effectively using “stable” without needing to use only stable features? Years ago I was aware of some projects that did that as a really trivial way to select a “blessed” version without needing to think about it.
… On Jun 14, 2021, at 19:06, Joshua Nelson ***@***.***> wrote:
Pinning a nightly is tracked by #228, not here.
I am not willing to have the docs.rs team be in charge of finding a "blessed" nightly that works for everyone, we don't have the time or manpower to be responsible for that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@TheBlueMatt building rustc from source takes about 45 minutes on consumer hardware, and we would need somewhere to store the artifacts. There is no nightly that corresponds to stable because it will be missing backports, and it means a great deal more complexity for the team because it introduces a 6-12 week delay between when features are introduced to rustdoc and docs.rs can start using them. So I don't consider that a good alternative at this time, I think pinning nightlies is much more feasible. |
If anyone is following this issue because they want standard library types in signatures and data structures to link to https://doc.rust-lang.org/std, instead of https://doc.rust-lang.org/nightly/std like they do today in docs built by docs.rs, you can accomplish that by adding: # Cargo.toml
[package.metadata.docs.rs]
rustdoc-args = [
"--extern-html-root-url=core=https://doc.rust-lang.org",
"--extern-html-root-url=alloc=https://doc.rust-lang.org",
"--extern-html-root-url=std=https://doc.rust-lang.org",
"--extern-html-root-url=proc_macro=https://doc.rust-lang.org",
] |
https://docs.rs/crate/abi_stable/0.8.0/builds
abi_stable
https://docs.rs/crate/abi_stable/0.8.0/builds/203164
It also failed on my computer (in nightly-2019-12-03-x86_64-unknown-linux-gnu) with the same error and this backtrace
Backtrace
This seems to be the same bug as rust-lang/rust#67006.
cargo doc
runs fine on stable-x86_64-unknown-linux-gnu - rustc 1.39.0 (4560ea788 2019-11-04).The text was updated successfully, but these errors were encountered: