mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

mention stable-in-unstable issue

This commit is contained in:
Ralf Jung 2019-08-25 10:22:14 +02:00 committed by Who? Me?!
parent 53c99c90bd
commit f98ca2953f
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/stability.md
View File

@ -16,6 +16,13 @@ You can make specific sub-items stable by using the `#[stable]` attribute on the
The stability scheme works similarly to how `pub` works. You can have public functions of The stability scheme works similarly to how `pub` works. You can have public functions of
nonpublic modules and you can have stable functions in unstable modules or vice versa. nonpublic modules and you can have stable functions in unstable modules or vice versa.
Note, however, that due to a [rustc bug], stable items inside unstable modules
*are* available to stable code in that location! So, for example, stable code
can import `core::intrinsics::transmute` even though `intrinsics` is an unstable
module. Thus, this kind of nesting should be avoided when possible.
[rustc bug]: https://github.com/rust-lang/rust/issues/15702
# stable # stable
The `#[stable(feature = "foo", "since = "1.420.69")]` attribute explicitly marks an item as The `#[stable(feature = "foo", "since = "1.420.69")]` attribute explicitly marks an item as