Skip to content

Commit

Permalink
Followup to rust-lang#1862
Browse files Browse the repository at this point in the history
First, I'm sorry, I realize a sentence was not correctly ended in rust-lang#1862.

Then, after re-reading UI documentation, I hope to slightly improve the
documentation once again (at least, assuming that this time I totally understood
how it works).
  • Loading branch information
Arthur-Milchior committed Jan 27, 2024
1 parent a79d236 commit 8021e7b
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions src/incrcomp-debugging.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,10 @@ fn bar() { foo(); }
```

This should be read as
> If this (`foo`) is changed, then this (i.e. `bar`)'s TypeckTables would need
to be changed. Also, this
> If this (`foo`) is changed, then this (i.e. `bar`)'s TypeckTables would need to be changed.
Technically, what occurs is that the test is expected to emit the string "OK" on
stderr, associated to this line.

You could also add the lines

Expand All @@ -33,7 +35,8 @@ fn baz() { }
```

Whose meaning is
> If `foo` is changed, then `baz`'s TypeckTables does not need to be changed, as there is no path.
> If `foo` is changed, then `baz`'s TypeckTables does not need to be changed.
> There command-line stderr should contains the string "no path".
Recall that the `//~ ERROR OK` is a comment from the point of view of the Rust
code we test, but is meaningful from the point of view of the test itself.
Expand Down

0 comments on commit 8021e7b

Please sign in to comment.