I was proposing something similar in this thread:
Summary
In addition to stable and unstable feature statuses introduce an additional “semi-stable” status. While technically it will be equivalent to unstable, the responsible team announces that feature in question is ready for stabilization and no breaking changes are planned, so all interested parties are welcomed to use the feature and even publish crates which use it. In other words, while it’s possible that breaking changes will be introduced to semi-stable feature (e.g. if serious flaw wil…
One of the concerns was adding notion of features to stable lang, this is why one of the alternatives developed during discussion was to move enabling of features to Cargo.toml.
1 Like