3 ms·

The bug is https://github.com/rust-lang/reference/issues/487 https://github.com/rust-lang/reference/issues/487 I'm not quite sure how it got to be that way, as

The bug is https://github.com/rust-lang/reference/issues/487 https://github.com/rust-lang/reference/issues/487 I'm not quite sure how it got to be that way, as the policy is that reference documentation is supposed to be written (if not actually in place) by the time a feature is stabilised. (I know you know this, because you wrote that policy.)

steveklabnik 7y ago
Thanks! I wonder if it's been updated and the issue has not been closed, but I will take a look this week. Someone else wrote it actually! But, we ended up relaxing it recently, due to build system concerns. Polyrepos are hard :/
- mjw1007 7y ago
  It has not been updated. use-declarations.md was updated three days ago to replace incorrect text with a note saying «Note: This section is incomplete» though. I understand why build system trouble meant the policy was changed from "the documentation must be in place" to "the documentation must be written". I do not understand why anything prevents the stabilisation process including a checklist item confirming that the documentation has been at least drafted.
  - steveklabnik 7y ago
    I only glanced at it but saw a "differences from rust 2015" section and that would indicate to me that it got updated somehow. Regardless, I'll look into it for real, so we'll get it sorted either way. > I do not understand why anything prevents the stabilisation process including a checklist item confirming that the documentation has been at least drafted. Nothing really, but we have bigger designs for the RFC process ("staged RFCs") that would introduce this, and so I haven't pushed for it in the meantime as its own separate thing.
    - mjw1007 7y ago
      It was updated for the half-way-house 2018-edition changes in Rust 1.31 (in December 2018). It wasn't updated for the further changes ("uniform paths") made six weeks later in Rust 1.32.

steveklabnik 7y ago

Thanks! I wonder if it's been updated and the issue has not been closed, but I will take a look this week. Someone else wrote it actually! But, we ended up relaxing it recently, due to build system concerns. Polyrepos are hard :/

mjw1007 7y ago
It has not been updated. use-declarations.md was updated three days ago to replace incorrect text with a note saying «Note: This section is incomplete» though. I understand why build system trouble meant the policy was changed from "the documentation must be in place" to "the documentation must be written". I do not understand why anything prevents the stabilisation process including a checklist item confirming that the documentation has been at least drafted.
- steveklabnik 7y ago
  I only glanced at it but saw a "differences from rust 2015" section and that would indicate to me that it got updated somehow. Regardless, I'll look into it for real, so we'll get it sorted either way. > I do not understand why anything prevents the stabilisation process including a checklist item confirming that the documentation has been at least drafted. Nothing really, but we have bigger designs for the RFC process ("staged RFCs") that would introduce this, and so I haven't pushed for it in the meantime as its own separate thing.
  - mjw1007 7y ago
    It was updated for the half-way-house 2018-edition changes in Rust 1.31 (in December 2018). It wasn't updated for the further changes ("uniform paths") made six weeks later in Rust 1.32.