about summary refs log tree commit diff
path: root/tests/ui/rmeta
AgeCommit message (Collapse)AuthorLines
2025-04-03compiletest: Require `//~` annotations even if `error-pattern` is specifiedVadim Petrochenkov-2/+4
2025-04-01Make missing optimized MIR error more informativeOli Scherer-2/+2
2025-03-25compiletest: Support matching on diagnostics without a spanVadim Petrochenkov-0/+2
2025-03-07Support rmeta inputs for --crate-type=bin --emit=objSam McCall-0/+32
This already works for --emit=metadata, but is possible anytime we're not linking. Tests: `rmeta_bin` checks we're not changing --emit=link (already passes) `rmeta_bin-pass` tests the new behavior for --emit=obj (would fail today) and also --emit=metadata which isn't changing
2025-03-04tests: rebless some tests as a side-effect of `TEST_BUILD_DIR` changes许杰友 Jieyou Xu (Joe)-1/+1
2025-02-10Show diff suggestion format on verbose replacementEsteban Küber-2/+3
``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 | LL | let _ = 2.l; | ^ | help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix | LL - let _ = 2.l; LL + let _ = 2.0f64; | ```
2025-01-27Remove all dead files inside tests/ui/León Orell Valerian Liehr-1/+0
2024-02-16[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives许杰友 Jieyou Xu (Joe)-30/+30
2023-11-24Show number in error message even for one errorNilstrieb-4/+4
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-11-21Auto merge of #115691 - jsgf:typed-json-diags, r=est31,dtolnaybors-1/+1
Add `$message_type` field to distinguish json diagnostic outputs Currently the json-formatted outputs have no way to unambiguously determine which kind of message is being output. A consumer can look for specific fields in the json object (eg "message"), but there's no guarantee that in future some other kind of output will have a field of the same name. This PR adds a `"type"` field to add json outputs which can be used to unambiguously determine which kind of output it is. The mapping is: `diagnostic`: regular compiler diagnostics `artifact`: artifact notifications `future_incompat`: Future incompatibility report `unused_extern`: Unused crate warnings/errors This matches the "internally tagged" representation for serde enums.
2023-11-18tweak logic of "unknown field" labelEsteban Küber-1/+6
2023-10-13Use `$message_type` as the tagJeremy Fitzhardinge-1/+1
`type` turned out to be controversial.
2023-09-19Add `type` field to json diagnostic outputsJeremy Fitzhardinge-1/+1
Currently the json-formatted outputs have no way to unambiguously determine which kind of message is being output. A consumer can look for specific fields in the json object (eg "message"), but there's no guarantee that in future some other kind of output will have a field of the same name. This PR adds a `"type"` field to add json outputs which can be used to unambiguously determine which kind of output it is. The mapping is: diagnostic: regular compiler diagnostics artifact: artifact notifications future_incompat: Report of future incompatibility unused_extern: Unused crate warnings/errors This matches the "internally tagged" representation for serde enums.
2023-08-30Emit error instead of ICE when optimized MIR is missingMartin Nordholts-0/+25
Closes 51388.
2023-07-19Rewrite rmeta-rpass test to work with the new check for all crate sources ↵bjorn3-35/+0
being in sync
2023-01-11Move /src/test to /testsAlbert Larsan-0/+163
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 18:08:22 +0000