diff options
| author | bors <bors@rust-lang.org> | 2024-06-17 21:32:16 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-06-17 21:32:16 +0000 |
| commit | 59e2c01c2217a01546222e4d9ff4e6695ee8a1db (patch) | |
| tree | 169a3936cf296ecffe84f6fff35d05dd3fff8d00 /compiler/rustc_parse/src/parser/expr.rs | |
| parent | 04ab7b2be0db3e6787f5303285c6b2ee6279868d (diff) | |
| parent | 6228b3e40e78ca0a29fd4599c9b7a3e340bb1572 (diff) | |
| download | rust-59e2c01c2217a01546222e4d9ff4e6695ee8a1db.tar.gz rust-59e2c01c2217a01546222e4d9ff4e6695ee8a1db.zip | |
Auto merge of #125500 - Oneirical:bundle-them-up-why-not, r=jieyouxu
Migrate `link-arg`, `link-dedup` and `issue-26092` `run-make` tests to `rmake` format Part of #121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). All of these tests check if rustc's output contains (or does not) contain certain strings. Does that mean these could be better suited to becoming UI/codegen tests? try-job: x86_64-msvc
Diffstat (limited to 'compiler/rustc_parse/src/parser/expr.rs')
0 files changed, 0 insertions, 0 deletions