diff options
| author | bors <bors@rust-lang.org> | 2024-05-06 03:31:30 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-05-06 03:31:30 +0000 |
| commit | 96f1da82687f499dd3f57006ae71548714532382 (patch) | |
| tree | 83ffb42104f807be2d38838f2f78fcef1732b929 /compiler/rustc_codegen_llvm/src | |
| parent | 80420a693f89ce4201a8e43b8d5191c7ee0fa368 (diff) | |
| parent | 2acbe9c7438478b022fa52e54ba3ceb8ca570c20 (diff) | |
| download | rust-96f1da82687f499dd3f57006ae71548714532382.tar.gz rust-96f1da82687f499dd3f57006ae71548714532382.zip | |
Auto merge of #124638 - nnethercote:mv-expand-tests, r=compiler-errors
Move some tests from `rustc_expand` to `rustc_parse`. There are some test cases involving `parse` and `tokenstream` and `mut_visit` that are located in `rustc_expand`. Because it used to be the case that constructing a `ParseSess` required the involvement of `rustc_expand`. However, since #64197 merged (a long time ago) `rust_expand` no longer needs to be involved. This commit moves the tests into `rustc_parse`. This is the optimal place for the `parse` tests. It's not ideal for the `tokenstream` and `mut_visit` tests -- they would be better in `rustc_ast` -- but they still rely on parsing, which is not available in `rustc_ast`. But `rustc_parse` is lower down in the crate graph and closer to `rustc_ast` than `rust_expand`, so it's still an improvement for them. The exact renaming is as follows: - rustc_expand/src/mut_visit/tests.rs -> rustc_parse/src/parser/mut_visit/tests.rs - rustc_expand/src/tokenstream/tests.rs -> rustc_parse/src/parser/tokenstream/tests.rs - rustc_expand/src/tests.rs + rustc_expand/src/parse/tests.rs -> compiler/rustc_parse/src/parser/tests.rs The latter two test files are combined because there's no need for them to be separate, and having a `rustc_parse::parser::parse` module would be weird. This also means some `pub(crate)`s can be removed. r? `@compiler-errors`
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
