-
Notifications
You must be signed in to change notification settings - Fork 548
proposed copy edits to rustdoc chapter #150
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
Conversation
So doxidize is officially the future rustdoc 2? |
@steveklabnik ^^ What, if anything, should be said about future-rustdoc? |
I think, for now, we should simply remove the references to this project. It's not in a state where we want people to poke at it, and it's not going to be until the fall, at least. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks :)
src/rustdoc.md
Outdated
@@ -4,7 +4,7 @@ Rustdoc actually uses the rustc internals directly. It lives in-tree with the | |||
compiler and standard library. This chapter is about how it works. (A new | |||
implementation is also [under way], though). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you change this to something more vague (as per #150 (comment))
Perhaps something like "There have been some attempts to rewrite rustdoc, but they are in early stages".
Ping @zackmdavis |
The current directory is typically not on the user's $PATH.
Steve says it's not ready (rust-lang#150 (comment)).
580b72c
to
824c5c2
Compare
@mark-i-m pong (just scrapped the sentence entirely) |
Thanks! |
(updating a link, and making commands more literally copy-pasteable)