Some writing improvement, conciseness of intro
This commit is contained in:
parent
cb6fafbdf3
commit
caf7126ee8
1 changed files with 3 additions and 4 deletions
|
@ -1,9 +1,8 @@
|
|||
# Unstable features
|
||||
|
||||
Rustdoc is under active development, and like the Rust compiler, some features are only available
|
||||
on the nightly releases. Some of these are new and need some more testing before they're able to get
|
||||
released to the world at large, and some of them are tied to features in the Rust compiler that are
|
||||
themselves unstable. Several features here require a matching `#![feature(...)]` attribute to
|
||||
on nightly releases. Some of these features are new and need some more testing before they're able to be
|
||||
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
|
||||
enable, and thus are more fully documented in the [Unstable Book]. Those sections will link over
|
||||
there as necessary.
|
||||
|
||||
|
@ -428,4 +427,4 @@ $ rustdoc src/lib.rs --test -Z unstable-options --persist-doctests target/rustdo
|
|||
|
||||
This flag allows you to keep doctest executables around after they're compiled or run.
|
||||
Usually, rustdoc will immediately discard a compiled doctest after it's been tested, but
|
||||
with this option, you can keep those binaries around for farther testing.
|
||||
with this option, you can keep those binaries around for farther testing.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue