mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Followup to #1862 (#1864)

This commit is contained in:
Arthur Milchior 2024-01-27 22:12:41 +01:00 committed by GitHub
parent a79d2364e7
commit 5a7b5f8643
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/incrcomp-debugging.md
View File

@ -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
@ -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.
> The macro must emit an error, and the error message must contains "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.