Skip to content

Host compiler documentation #29893

Closed
Closed

Description

@brson

The API documentation for the compiler is useful, and only available online via @Manishearth. It should be hosted by rust-lang.

Need to decide where on the doc server they are hosted - probably separately from the end-user docs; ensure the makefiles can produce them in a separate location from the user docs; add the build rule to the dist builders; make buildbot upload them to the right place.

cc @edunham

UPDATE: Mentoring instructions available here.

Activity

  1. steveklabnik commented on Nov 17, 2015

    @steveklabnik
    Contributor

    This is a dup of #28309, but gets to the heart of the issue, so I'm going to close it in favor of this one.

    I've been talking with @edunham about this a few times over the last few weeks, I think the plan we discussed was a /internals path.

  2. edunham commented on Nov 24, 2015

    @edunham
    Contributor

    @Manishearth how are you currently generating the contents of https://github.com/Manishearth/rust-internals-docs ?

  3. Manishearth commented on Nov 24, 2015

    @Manishearth
    Member

    ./configure --enable-compiler-docs; make docs. I was considering at some point to make it turn on private docs as well (using rustdoc --passes)

  4. added
    T-dev-toolsRelevant to the dev-tools subteam, which will review and decide on the PR/issue.
    on May 24, 2017
  5. 29 remaining items

  6. added a commit that references this issue on Mar 23, 2018
    6986057
  7. davidtwco commented on Mar 24, 2018

    @davidtwco
    Member

    Re-opening as this still depends on this rust-lang/rust-central-station#40 to land.

  8. SimonSapin commented on Apr 4, 2018

    @SimonSapin
    Contributor

    https://doc.rust-lang.org/nightly/nightly-rustc/rustc/ is up. Should it use RUSTDOCFLAGS="--document-private-items"?

  9. davidtwco commented on Apr 4, 2018

    @davidtwco
    Member

    @alexcrichton @SimonSapin I agree that this would be very useful, I've submitted a PR that should handle this: #49654.

  10. kennytm commented on Apr 4, 2018

    @kennytm
    Member

    If we are documenting private items, I hope rustdoc can clearly indicate that an item is private (or pub(crate) or whatever restriction). For instance, if I'm working in the rustc_mir crate, I would not want to know any private detail about the syntax_pos crate.

    Also, I hope there's a -Z flag to tell rustdoc to shut up about the rustc_private feature, because we all know the compiler API is unstable 😄.

    cc @rust-lang/docs

  11. Manishearth commented on Apr 4, 2018

    @Manishearth
    Member

    I've long wanted --document-private-items to produce a "Private" checkbox that lets you toggle private items as well. Maybe I'll work on that if @QuietMisdreavus thinks its a good idea

  12. mark-i-m commented on Apr 4, 2018

    @mark-i-m
    Contributor

    Also, I hope there's a -Z flag to tell rustdoc to shut up about the rustc_private feature, because we all know the compiler API is unstable smile.

    I would appreciate that, since those little yellow boxes take up a lot of space...

    EDIT: and all of the [Experimental] notes everywhere...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-feature-requestCategory: A feature request, i.e: not implemented / a PR.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.P-mediumMedium priorityT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions