diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-03-21 06:56:49 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-21 06:56:49 +0100 |
| commit | 5ba395a98bfab0f9025ebf477ece0d58c396ba60 (patch) | |
| tree | 1d7c4769ff3c54645b2dd57ac3511126ff09a93b /compiler/rustc_target/src | |
| parent | 4447953fdd6eadc44db57c3b580c9553b57169f5 (diff) | |
| parent | ff46ea8253d2d57882de708b281b471fb446cd1d (diff) | |
| download | rust-5ba395a98bfab0f9025ebf477ece0d58c396ba60.tar.gz rust-5ba395a98bfab0f9025ebf477ece0d58c396ba60.zip | |
Rollup merge of #138754 - oli-obk:push-vtqtnwluyxop, r=compiler-errors
Handle spans of `~const`, `const` and `async` trait bounds in macro expansion r? `@compiler-errors` `visit_span` is actually only used in one place (the `transcribe::Marker`), and all of this syntax is unstable, so while it would still be nice to write a test for it, I wager there's lots more interesting things in `transcribe::Marker` to write tests for. And the worst is some diagnostics being weird or incremental being not as incremental as it could be
Diffstat (limited to 'compiler/rustc_target/src')
0 files changed, 0 insertions, 0 deletions