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
librustdoc used to be distributed with other compiler crates and could be found in the sysroot. This is no longer the case which breaks any crate which does extern crate rustdoc;.
I assume this wasn't intentional and is due to the changes with how rustdoc is being built.
did you have tools using extern crate rustdoc out of tree?
Yes, rustw does. It only uses its markdown rendering though. I'd assume I could pull that into an external crate, but iirc, the last time I tried that it was tied into rustdoc and compiler internals in weird ways.
I'll look into that - I assume Steve will have to solve a similar problem for new rustdoc, so maybe I can use that?
Well, if it's not working out to migrate to either the new rustdoc or otherwise solve the problem, let us know and we can discuss making librustdoc remain in the sysroot.
Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!
See this document for info about what commands tagged team members can give me.
Activity
alexcrichton commentedon Aug 8, 2017
Hm this was indeed intentional, all due to #43482. That being said, it wasn't intended to break things!
@nrc did you have tools using
extern crate rustdocout of tree? That's sort of something I'd hope that we wouldn't have to keep working :(Mark-Simulacrum commentedon Aug 8, 2017
Yes, this was indeed intentional. We can technically fix this I think if we need to, but I'd prefer not to -- it'd be a bit of a hack.
nrc commentedon Aug 8, 2017
Yes, rustw does. It only uses its markdown rendering though. I'd assume I could pull that into an external crate, but iirc, the last time I tried that it was tied into rustdoc and compiler internals in weird ways.
I'll look into that - I assume Steve will have to solve a similar problem for new rustdoc, so maybe I can use that?
Mark-Simulacrum commentedon Aug 9, 2017
Well, if it's not working out to migrate to either the new rustdoc or otherwise solve the problem, let us know and we can discuss making librustdoc remain in the sysroot.
Mark-Simulacrum commentedon Sep 15, 2017
@rfcbot fcp close
Let's see if this works...
If not, I'll just close; I don't think this is going to change. rustdoc is unstable, and shouldn't really be used for markdown rendering anyway...
rfcbot commentedon Sep 15, 2017
Team member @Mark-Simulacrum has proposed to close this. The next step is review by the rest of the tagged teams:
No concerns currently listed.
Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!
See this document for info about what commands tagged team members can give me.
steveklabnik commentedon Sep 15, 2017
I was planning on publishing on crates.io, honestly.
rfcbot commentedon Feb 16, 2018
🔔 This is now entering its final comment period, as per the review above. 🔔
rfcbot commentedon Feb 26, 2018
The final comment period is now complete.
Mark-Simulacrum commentedon Jun 12, 2018
Closing as per concluded FCP.