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.

Sign up for GitHub

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

Jump to bottom

Rustdoc on private crate gives infinite redirect loop #18715

Closed
Manishearth opened this issue Nov 6, 2014 · 1 comment
Closed

Rustdoc on private crate gives infinite redirect loop #18715

Manishearth opened this issue Nov 6, 2014 · 1 comment

Comments

@Manishearth
Copy link
Member

While looking for a different rustdoc bug, I found that the following lib.rs

#[test]
fn it_works() {
}


trait Y{}

impl Y for Option<uint>{}

(cargo new foo followed by adding a trait and an impl to the lib.rs)

produces the following doc/lib/index.html:

<!DOCTYPE html>
<html lang="en">
<head>
    <meta http-equiv="refresh" content="0;URL=../lib/index.html">
</head>
<body>
</body>
</html>

which is just an infinite redirect.

While the crate being empty (externally, due to all private items) means that rustdoc is pretty useless to run, I don't think it should fail into an infinite redirect, which is just confusing.

This doesn't happen if I replace Option with a struct defined within the same crate.
@ghost
Copy link

ghost commented Nov 6, 2014

Dupe of #16265. Thanks!

@ghost ghost closed this as completed Nov 6, 2014
lnicola pushed a commit to lnicola/rust that referenced this issue Dec 23, 2024
@Veykril
Merge pull request rust-lang#18715 from aibaars/ungram-asm-option

Unverified

The signature in this commit could not be verified. Someone may be trying to trick you.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode
4aa34ab 
Fix AsmOption rule in rust.ungram
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Manishearth