Skip to content

Commit ee9164a

Browse files
Fix typos
1 parent e679523 commit ee9164a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

text/0000-inline-const.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ fn foo() -> &u32 {
6060
}
6161
```
6262

63-
Writing out a `const` declaration everytime we need a long-lived reference or
63+
Writing out a `const` declaration every time we need a long-lived reference or
6464
a non-`Copy` array initializer can be annoying. To improve the situation,
6565
[RFC 1414] introduced rvalue static promotion to extend lifetimes, and
6666
[RFC 2203] extended the concept of promotion to array initializers.
@@ -268,7 +268,7 @@ approach](https://github.com/rust-lang/rust/pull/70042#issuecomment-612221597)
268268
instead.
269269

270270
It would also possible to separate out the parts of this RFC relating to patterns
271-
so that they can be decided upon seperately.
271+
so that they can be decided upon separately.
272272

273273
# Prior art
274274
[prior-art]: #prior-art
@@ -333,7 +333,7 @@ currently allow nested `const` declarations. Whether to lint against inline
333333
[future possibilities]: #future-possibilities
334334

335335
It would be possible to allow the syntax `const expr` for an inline `const` that
336-
consists of a single expression. This is analagous to the single expression
336+
consists of a single expression. This is analogous to the single expression
337337
variant of closures: `|| 42`. This is backwards compatible with the current proposal.
338338

339339
At some point (an edition boundary?), we may want to narrow the scope of

0 commit comments

Comments
 (0)