Skip to content
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

mk: don't build docs for internal or behind-the-facade crates #23848

Merged
merged 1 commit into from
Mar 30, 2015
Merged

mk: don't build docs for internal or behind-the-facade crates #23848

merged 1 commit into from
Mar 30, 2015

Conversation

emberian
Copy link
Member

This saves a bunch of a time and will make distributions smaller, as well as
avoiding filling the implementors page with internal garbage. Turn it back on
with --enable-compiler-docs if you want them.

(Crates behind the facade are not documented at all)

[breaking-change]

…/stable

This saves a bunch of a time and will make distributions smaller, as well as
avoiding filling the implementors page with internal garbage. Turn it back on
with `--enable-compiler-docs` if you want compiler docs during development.

Crates behind the facade are only documented on nightly/dev builds (where they
can be used).

[breaking-change]

Closes #23772
Closes #21297
@rust-highfive
Copy link
Collaborator

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

@huonw
Copy link
Member

huonw commented Mar 29, 2015

Doesn't this mean that core etc. never have their own explicit documentation?

@emberian
Copy link
Member Author

@huonw Indeed not. I'll add a cfg for that (probably keying off whether the channel is stable/beta/nightly)

@@ -526,7 +526,8 @@ VAL_OPTIONS=""
opt valgrind 0 "run tests with valgrind (memcheck by default)"
opt helgrind 0 "run tests with helgrind instead of memcheck"
opt valgrind-rpass 1 "run rpass-valgrind tests with valgrind"
opt docs 1 "build documentation"
opt docs 1 "build standard libraary documentation"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extraa a

@huonw
Copy link
Member

huonw commented Mar 30, 2015

r=me with minor nits.

@emberian
Copy link
Member Author

@bors: r=huonw rollup

@bors
Copy link
Contributor

bors commented Mar 30, 2015

📌 Commit e64b677 has been approved by huonw

@steveklabnik
Copy link
Member

🎊

@alexcrichton
Copy link
Member

Hm, was it considered that most [src] links will break? The only way for them to work currently is to link back to the code in the original crate, so this will cause it so many of them unfortunately break due to being under the facade.

@bors
Copy link
Contributor

bors commented Mar 30, 2015

⌛ Testing commit e64b677 with merge 14192d6...

bors added a commit that referenced this pull request Mar 30, 2015
This saves a bunch of a time and will make distributions smaller, as well as
avoiding filling the implementors page with internal garbage. Turn it back on
with `--enable-compiler-docs` if you want them.

(Crates behind the facade are not documented at all)

[breaking-change]
@bors bors merged commit e64b677 into rust-lang:master Mar 30, 2015
@emberian
Copy link
Member Author

@alexcrichton That is quite unfortunate...

@steveklabnik
Copy link
Member

Ahhh

@alexcrichton
Copy link
Member

Actually on second thought this also breaks all cross-crate links to Vec, for example. Right now a cross-crate link to Vec only knows that it was defined in libcollections, not that it was reexported in the standard library.

I think that these two downsides are pretty serious, @cmr would you be ok reverting the "don't build docs for facade crates" part of this PR?

@emberian
Copy link
Member Author

@alexcrichton yeah, I'll back that bit out.

@alexcrichton
Copy link
Member

Ok, thanks @cmr!

@steveklabnik
Copy link
Member

This broke so many links in documentation: #14515 (comment)

@emberian
Copy link
Member Author

emberian commented Apr 1, 2015

@steveklabnik what docs link to compiler crates?

@steveklabnik
Copy link
Member

We have an 'unstable' section of the book, and one of the chapters documents syntax extensions.

@pnkfelix
Copy link
Member

( I think @cmr's aforementioned "back that bit out" commit was this one: b314fed )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants