Define what the stability attributes mean

[emberian]

Exactly what do each of the stability attributes mean?

I think #[stable] should mean "no change to this will break source compatability with safe code" and #[frozen] should mean "this type will not change in any way to break source or binary compatability with safe or unsafe code". This includes size and representation.

[emberian]

Nominating for 1.0, this affects how we specify and maintain stability.

[brson]

Just copy this somewhere Rusty http://nodejs.org/api/documentation.html#documentation_stability_index, with proper attribution of course. Though I think we should probably drop 'frozen' and 'locked' until we need them.

[emberian]

I don't think locked is necessary, but I think frozen is definitely
necessary. I think having a separate level of stability for guaranteed ABI
compat is incredibly useful.

On Tue, Feb 11, 2014 at 9:16 PM, Brian Anderson notifications@github.comwrote:

Just copy this somewhere Rusty
http://nodejs.org/api/documentation.html#documentation_stability_index,
with proper attribution of course. Though I think we should probably drop
'frozen' and 'locked' until we need them.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12203#issuecomment-34832159
.

[pnkfelix]

We do need to define what these attributes mean for 1.0, as part of the docs 1.0. Accepted for P-backcompat-libs.

[huonw]

This exists: http://static.rust-lang.org/doc/master/rust.html#stability

The precise definitions could use some tuning (I just took them directly from NodeJS), but it's there...

[steveklabnik]

Yup, they're here. They seem fine to me. Does this deserve an RFC or something? Can we close this?

[emberian]

Yes.