Skip to content

Commit c57b3a0

Browse files
committed
Fix some invalid language tags
This fixes some code block tags that aren't using the correct language for rust.
1 parent 34463b7 commit c57b3a0

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

src/borrow_check/two_phase_borrows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ two-phase borrow are:
1515

1616
To give some examples:
1717

18-
```rust2018
18+
```rust,edition2018
1919
// In the source code
2020
2121
// Case 1:

src/coroutine-closures.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ We introduce a `AsyncFnKindHelper` trait which allows us to defer the question o
167167

168168
This seems a bit roundabout and complex, and I admit that it is. But let's think of the "do nothing" alternative -- we could instead mark all `AsyncFn*` goals as ambiguous until upvar analysis, at which point we would know exactly what to put into the upvars of the coroutine we return. However, this is actually *very* detrimental to inference in the program, since it means that programs like this would not be valid:
169169

170-
```rust!
170+
```rust,ignore
171171
let c = async || -> String { .. };
172172
let s = c().await;
173173
// ^^^ If we can't project `<{c} as AsyncFn>::call()` to a coroutine, then the `IntoFuture::into_future` call inside of the `.await` stalls, and the type of `s` is left unconstrained as an infer var.

0 commit comments

Comments
 (0)