reference Should we document when features are stabilized?

The standard library documentation documents what version that various types, functions, and what not are stabilized. Since there's no "API docs" for features, other than this reference, should we be documenting when language features are stabilized into the reference?

May 23 '17 00:05 Havvy

Even though we haven't done this in the past: think pre 1.0. I don't see why this can't be done post 1.0. I have written some thought concerning this topic here: https://internals.rust-lang.org/t/life-after-an-rfc/4126

Edit: Oh I misread this issue for updating RFCs upon stabilization... 😒

May 23 '17 00:05 cbreeden

This document seems to suggest "yes": https://github.com/rust-lang-nursery/rust-forge/blob/master/stabilization-guide.md#updating-documentation

May 23 '17 01:05 est31

@est31 that document says nothing about this topic, that I'm aware of.

@Havvy historically we haven't done this; I'm not totally opposed but there are some problems; for example, if features are modified, it's not clear to me how to do this on a fine-grained enough basis.

May 23 '17 13:05 steveklabnik

This is related to https://github.com/rust-lang/rust/issues/44894

Dec 08 '17 19:12 Havvy