Spelling - compiler
* account * achieved * advising * always * ambiguous * analysis * annotations * appropriate * build * candidates * cascading * category * character * clarification * compound * conceptually * constituent * consts * convenience * corresponds * debruijn * debug * debugable * debuggable * deterministic * discriminant * display * documentation * doesn't * ellipsis * erroneous * evaluability * evaluate * evaluation * explicitly * fallible * fulfill * getting * has * highlighting * illustrative * imported * incompatible * infringing * initialized * into * intrinsic * introduced * javascript * liveness * metadata * monomorphization * nonexistent * nontrivial * obligation * obligations * offset * opaque * opportunities * opt-in * outlive * overlapping * paragraph * parentheses * poisson * precisely * predecessors * predicates * preexisting * propagated * really * reentrant * referent * responsibility * rustonomicon * shortcircuit * simplifiable * simplifications * specify * stabilized * structurally * suggestibility * translatable * transmuting * two * unclosed * uninhabited * visibility * volatile * workaround Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
parent
31656e7295
commit
e09d0d2a29
101 changed files with 159 additions and 159 deletions
|
@ -1,4 +1,4 @@
|
|||
A struct pattern attempted to extract a non-existent field from a struct.
|
||||
A struct pattern attempted to extract a nonexistent field from a struct.
|
||||
|
||||
Erroneous code example:
|
||||
|
||||
|
|
|
@ -32,7 +32,7 @@ error: [-, o]
|
|||
This error is deliberately triggered with the `#[rustc_variance]` attribute
|
||||
(`#![feature(rustc_attrs)]` must be enabled) and helps to show you the variance
|
||||
of the type's generic parameters. You can read more about variance and
|
||||
subtyping in [this section of the Rustnomicon]. For a more in depth look at
|
||||
subtyping in [this section of the Rustonomicon]. For a more in depth look at
|
||||
variance (including a more complete list of common variances) see
|
||||
[this section of the Reference]. For information on how variance is implemented
|
||||
in the compiler, see [this section of `rustc-dev-guide`].
|
||||
|
@ -41,6 +41,6 @@ This error can be easily fixed by removing the `#[rustc_variance]` attribute,
|
|||
the compiler's suggestion to comment it out can be applied automatically with
|
||||
`rustfix`.
|
||||
|
||||
[this section of the Rustnomicon]: https://doc.rust-lang.org/nomicon/subtyping.html
|
||||
[this section of the Rustonomicon]: https://doc.rust-lang.org/nomicon/subtyping.html
|
||||
[this section of the Reference]: https://doc.rust-lang.org/reference/subtyping.html#variance
|
||||
[this section of `rustc-dev-guide`]: https://rustc-dev-guide.rust-lang.org/variance.html
|
||||
|
|
|
@ -29,7 +29,7 @@ If `no_restriction()` were to use `&T` instead of `&()` as an argument, the
|
|||
compiler would have added an implied bound, causing this to compile.
|
||||
|
||||
This error can be resolved by explicitly naming the elided lifetime for `x` and
|
||||
then explicily requiring that the generic parameter `T` outlives that lifetime:
|
||||
then explicitly requiring that the generic parameter `T` outlives that lifetime:
|
||||
|
||||
```
|
||||
fn no_restriction<'a, T: 'a>(x: &'a ()) -> &'a () {
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
Plugin `..` only found in rlib format, but must be available in dylib format.
|
||||
|
||||
Erroronous code example:
|
||||
Erroneous code example:
|
||||
|
||||
`rlib-plugin.rs`
|
||||
```ignore (needs-linkage-with-other-tests)
|
||||
|
|
|
@ -10,7 +10,7 @@ trait Hello {
|
|||
}
|
||||
```
|
||||
|
||||
In this example, we tried to use the non-existent associated type `You` of the
|
||||
In this example, we tried to use the nonexistent associated type `You` of the
|
||||
`Hello` trait. To fix this error, use an existing associated type:
|
||||
|
||||
```
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
Attempted to access a non-existent field in a struct.
|
||||
Attempted to access a nonexistent field in a struct.
|
||||
|
||||
Erroneous code example:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue