Skip to content

Tuple struct fields missing in documented signatures #13594

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

Closed
SiegeLord opened this issue Apr 18, 2014 · 0 comments · Fixed by #13639
Closed

Tuple struct fields missing in documented signatures #13594

SiegeLord opened this issue Apr 18, 2014 · 0 comments · Fixed by #13639

Comments

@SiegeLord
Copy link
Contributor

E.g. a crate like this:

#![crate_type="lib"]
#![crate_id="test"]

pub struct A(int);
pub struct B(pub int);

Produces the following signatures:

pub struct A();
pub struct B();

I'd expect them to be something like:

pub struct A (
    // some fields omitted
);
pub struct B (int);
alexcrichton added a commit to alexcrichton/rust that referenced this issue Apr 20, 2014
The fields of tuple structs recently gained the ability to have privacy
associated with them, but rustdoc was not updated accodingly. This moves the
struct field filtering to the rendering phase in order to preserve the ordering
of struct fields to allow tuple structs to have their private fields printed as
underscores.

Closes rust-lang#13594
bors added a commit that referenced this issue Apr 20, 2014
…kler

The fields of tuple structs recently gained the ability to have privacy
associated with them, but rustdoc was not updated accodingly. This moves the
struct field filtering to the rendering phase in order to preserve the ordering
of struct fields to allow tuple structs to have their private fields printed as
underscores.

Closes #13594
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 a pull request may close this issue.

1 participant