API Documentation objectives for 1.6

[steveklabnik]

These are the parts of the API documentation that I'm going to try to handle during the 1.6 release. To start, I'm going to:

1. Keep it small. This is a new process, so I want to try to under-estimate, not over-estimate.
2. Focus on impact. This first round should be the stuff that's really, really important. It's all important, but still. More common stuff first.
3. Choose some things which I think may already be done. I've been putting a lot of work into Iterator lately, for example, so it's going here, because that way it can be checked off.

With that out of the way, here's the plan:

• home page #29330
• prelude #29369
• iter #29360
• char #29333
• std::char #29428
• str #29338
• string #29376

[steveklabnik]

#29552 is a regression in nightly that should be fixed before 1.6.

[steveklabnik]

#29552 is a regression in nightly that should be fixed before 1.6.

[steveklabnik]

Note, I'm checking the list off when I feel good about it, but aren't closing the issues until the week before the release. Want to go over them and make sure before it gets closed.

[steveklabnik]

Note, I'm checking the list off when I feel good about it, but aren't closing the issues until the week before the release. Want to go over them and make sure before it gets closed.

[steveklabnik]

Whew! regression fixed, and PRs submitted for the basics of all of this. Once they all land, I will do a once-over and make sure I'm happy with the results.

[steveklabnik]

Whew! regression fixed, and PRs submitted for the basics of all of this. Once they all land, I will do a once-over and make sure I'm happy with the results.

[steveklabnik]

Since 1.6 is now in beta, this can be closed. I'm not closing the individual issues due to conventions issues, just yet.

[steveklabnik]

Since 1.6 is now in beta, this can be closed. I'm not closing the individual issues due to conventions issues, just yet.