You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto merge of #58361 - GuillaumeGomez:rollup, r=GuillaumeGomez
Rollup of 16 pull requests
Successful merges:
- #57259 (Update reference of rlibc crate to compiler-builtins crate)
- #57740 (Use `to_ne_bytes` for converting IPv4Addr to octets)
- #57926 (Tiny expansion to docs for `core::convert`.)
- #58157 (Add Cargo.lock automatically adding message)
- #58203 (rustdoc: display sugared return types for async functions)
- #58243 (Add trait alias support in rustdoc)
- #58262 (Add #[must_use] message to Fn* traits)
- #58295 (std::sys::unix::stdio: explain why we do into_raw)
- #58297 (Cleanup JS a bit)
- #58317 (Some writing improvement, conciseness of intro)
- #58324 (miri: give non-generic functions a stable address)
- #58332 (operand-to-place copies should never be overlapping)
- #58345 (When there are multiple filenames, print what got interpreted as filenames)
- #58346 (rpath computation: explain why we pop())
- #58350 (Fix failing tidy (line endings on Windows))
- #58352 (miri value visitor: use `?` in macro)
Failed merges:
r? @ghost
Copy file name to clipboardExpand all lines: src/doc/rustdoc/src/unstable-features.md
+3-4
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
1
# Unstable features
2
2
3
3
Rustdoc is under active development, and like the Rust compiler, some features are only available
4
-
on the nightly releases. Some of these are new and need some more testing before they're able to get
5
-
released to the world at large, and some of them are tied to features in the Rust compiler that are
6
-
themselves unstable. Several features here require a matching `#![feature(...)]` attribute to
4
+
on nightly releases. Some of these features are new and need some more testing before they're able to be
5
+
released to the world at large, and some of them are tied to features in the Rust compiler that are unstable. Several features here require a matching `#![feature(...)]` attribute to
7
6
enable, and thus are more fully documented in the [Unstable Book]. Those sections will link over
0 commit comments