nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-12-04 12:44:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rollup merge of #133744 - HypheX:typo-fix, r=fmease

Browse Source 
Fix typo README.md

Fix typo README.md 2: Electric Boogaloo
Expands on #131144
This commit is contained in:
Guillaume Gomez 2024-12-02 17:36:09 +01:00 committed by GitHub
commit ed0880344c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
tests/ui/README.md
View File

@ -6,9 +6,9 @@ This folder contains `rustc`'s
## Test Directives (Headers)
Typically, a UI test will have some test directives / headers which are
special comments that tell compiletest how to build and intepret a test.
special comments that tell compiletest how to build and interpret a test.
As part of an on-going effort to rewrite compiletest
As part of an ongoing effort to rewrite compiletest
(see <https://github.com/rust-lang/compiler-team/issues/536>), a major
change proposal to change legacy compiletest-style headers `// <directive>`
to [`ui_test`](https://github.com/oli-obk/ui_test)-style headers
@ -30,6 +30,6 @@ but in `ui_test` style, the header would be written as
compiletest is changed to accept only `//@` directives for UI tests
(currently), and will reject and report an error if it encounters any
comments `// <content>` that may be parsed as an legacy compiletest-style
comments `// <content>` that may be parsed as a legacy compiletest-style
test header. To fix this, you should migrate to the `ui_test`-style header
`//@ <content>`.