auto merge of #14357 : huonw/rust/spelling, r=pnkfelix
The span on a inner doc-comment would point to the next token, e.g. the span for the `a` line points to the `b` line, and the span of `b` points to the `fn`.
```rust
//! a
//! b
fn bar() {}
```
This commit is contained in:
commit
02117dd1bc
21 changed files with 35 additions and 33 deletions
|
|
@ -8,7 +8,7 @@
|
|||
// option. This file may not be copied, modified, or distributed
|
||||
// except according to those terms.
|
||||
|
||||
//! Sharable mutable containers.
|
||||
//! Shareable mutable containers.
|
||||
//!
|
||||
//! Values of the `Cell` and `RefCell` types may be mutated through
|
||||
//! shared references (i.e. the common `&T` type), whereas most Rust
|
||||
|
|
@ -41,7 +41,7 @@
|
|||
//! preventing crash bugs. Because of that, inherited mutability is
|
||||
//! preferred, and interior mutability is something of a last
|
||||
//! resort. Since cell types enable mutation where it would otherwise
|
||||
//! be disallowed though, there are occassions when interior
|
||||
//! be disallowed though, there are occasions when interior
|
||||
//! mutability might be appropriate, or even *must* be used, e.g.
|
||||
//!
|
||||
//! * Introducing inherited mutability roots to shared types.
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ pub trait FormatWriter {
|
|||
/// This function will return an instance of `FormatError` on error.
|
||||
fn write(&mut self, bytes: &[u8]) -> Result;
|
||||
|
||||
/// Glue for usage of the `write!` macro with implementors of this trait.
|
||||
/// Glue for usage of the `write!` macro with implementers of this trait.
|
||||
///
|
||||
/// This method should generally not be invoked manually, but rather through
|
||||
/// the `write!` macro itself.
|
||||
|
|
|
|||
|
|
@ -872,10 +872,12 @@ pub trait OrdIterator<A> {
|
|||
/// `min_max` finds the minimum and maximum elements in the iterator.
|
||||
///
|
||||
/// The return type `MinMaxResult` is an enum of three variants:
|
||||
///
|
||||
/// - `NoElements` if the iterator is empty.
|
||||
/// - `OneElement(x)` if the iterator has exactly one element.
|
||||
/// - `MinMax(x, y)` is returned otherwise, where `x <= y`. Two values are equal if and only if
|
||||
/// there is more than one element in the iterator and all elements are equal.
|
||||
/// - `MinMax(x, y)` is returned otherwise, where `x <= y`. Two
|
||||
/// values are equal if and only if there is more than one
|
||||
/// element in the iterator and all elements are equal.
|
||||
///
|
||||
/// On an iterator of length `n`, `min_max` does `1.5 * n` comparisons,
|
||||
/// and so faster than calling `min` and `max separately which does `2 * n` comparisons.
|
||||
|
|
|
|||
|
|
@ -266,7 +266,7 @@ pub mod marker {
|
|||
#[deriving(Eq,Clone)]
|
||||
pub struct NoCopy;
|
||||
|
||||
/// A type which is considered "not sharable", meaning that
|
||||
/// A type which is considered "not shareable", meaning that
|
||||
/// its contents are not threadsafe, hence they cannot be
|
||||
/// shared between tasks.
|
||||
#[lang="no_share_bound"]
|
||||
|
|
|
|||
|
|
@ -260,7 +260,7 @@
|
|||
//! The suitability of `fail!` as an error handling mechanism is
|
||||
//! limited by Rust's lack of any way to "catch" and resume execution
|
||||
//! from a thrown exception. Therefore using failure for error
|
||||
//! handling requires encapsulating fallable code in a task. Calling
|
||||
//! handling requires encapsulating fallible code in a task. Calling
|
||||
//! the `fail!` macro, or invoking `fail!` indirectly should be
|
||||
//! avoided as an error reporting strategy. Failure is only for
|
||||
//! unrecoverable errors and a failing task is typically the sign of
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue