starred/hickory-dns

Fork 0

mirror of https://github.com/hickory-dns/hickory-dns.git synced 2026-04-25 11:15:54 +03:00

[GH-ISSUE #544] trust-dns-proto docs break #526

New issue

Closed

opened 2026-03-15 22:58:02 +03:00 by kerem · 6 comments

kerem commented

2026-03-15 22:58:02 +03:00

Owner

Originally created by @bspeice on GitHub (Aug 5, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/544

I'm unable to build documentation for some of my projects because they pull in trust-dns-proto, and the documentation breaks:

error[E0658]: access to extern crates through prelude is experimental (see issue #44660)
  |
  = help: add #![feature(extern_prelude)] to the crate attributes to enable

error: Could not document `trust-dns-proto`.

Is it possible to un-break things? I was under the impression that #![feature] flags require using a nightly compiler.

Originally created by @bspeice on GitHub (Aug 5, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/544 I'm unable to build documentation for some of my projects because they pull in trust-dns-proto, and the documentation breaks: ``` error[E0658]: access to extern crates through prelude is experimental (see issue #44660) | = help: add #![feature(extern_prelude)] to the crate attributes to enable error: Could not document `trust-dns-proto`. ``` Is it possible to un-break things? I was under the impression that `#![feature]` flags require using a nightly compiler.

kerem closed this issue

2026-03-15 22:58:07 +03:00

kerem commented

2026-03-15 22:58:13 +03:00

Author

Owner

@bluejekyll commented on GitHub (Aug 5, 2018):

To work around the nightly compiler errors, I use stable to generate docs, which works great: cargo +stable doc

As to this specific error, I haven’t looked into what would fix it on nightly.

@bluejekyll commented on GitHub (Aug 5, 2018): To work around the nightly compiler errors, I use stable to generate docs, which works great: `cargo +stable doc` As to this specific error, I haven’t looked into what would fix it on nightly.

kerem commented

2026-03-15 22:58:18 +03:00

Author

Owner

@bspeice commented on GitHub (Aug 5, 2018):

I'm not using nightly, this is happening on stable. Specifically, when I include actix in a project and re-run cargo doc I get the error above.

EDIT: Something went wrong in rustup, turns out I am in fact using the nightly compiler. Feel free to close if you want, I should've been on stable, but it may be worthwhile to leave this open to document that nightly docs break.

@bspeice commented on GitHub (Aug 5, 2018): I'm not using nightly, this is happening on stable. Specifically, when I include `actix` in a project and re-run `cargo doc` I get the error above. EDIT: Something went wrong in rustup, turns out I *am* in fact using the nightly compiler. Feel free to close if you want, I should've been on stable, but it may be worthwhile to leave this open to document that nightly docs break.

kerem commented

2026-03-15 22:58:23 +03:00

Author

Owner

@bluejekyll commented on GitHub (Aug 5, 2018):

Oddly, this used to happen to me often. On nightly and stable, I'm not seeing issues, current nightly:

rustc 1.29.0-nightly (97085f9fb 2018-08-01)

Not sure why I can't reproduce this right now.

@bluejekyll commented on GitHub (Aug 5, 2018): Oddly, this used to happen to me often. On nightly and stable, I'm not seeing issues, current nightly: `rustc 1.29.0-nightly (97085f9fb 2018-08-01)` Not sure why I can't reproduce this right now.

kerem commented

2026-03-15 22:58:28 +03:00

Author

Owner

@bspeice commented on GitHub (Aug 5, 2018):

I was on a 1.30 nightly if it makes any difference.

@bspeice commented on GitHub (Aug 5, 2018): I was on a 1.30 nightly if it makes any difference.

kerem commented

2026-03-15 22:58:33 +03:00

Author

Owner

@bspeice commented on GitHub (Aug 11, 2018):

Re-tried with most recent 1.30 nightly, no longer an issue. Going to consider this closed.

@bspeice commented on GitHub (Aug 11, 2018): Re-tried with most recent 1.30 nightly, no longer an issue. Going to consider this closed.

kerem commented

2026-03-15 22:58:38 +03:00

Author

Owner

@bluejekyll commented on GitHub (Aug 11, 2018):

Excellent. Thank you for following up!

@bluejekyll commented on GitHub (Aug 11, 2018): Excellent. Thank you for following up!