diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-10-23 06:51:23 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-23 06:51:23 +0200 |
| commit | 38eaf608eb9e0dddda1de1e03b08be123450e9b6 (patch) | |
| tree | 2bd845e115321cf52d99a6a16901fda272b0ff0b /compiler/rustc_mir_transform/src/coverage/mod.rs | |
| parent | b13176595d8a9fd27334747080764a53a18f4c24 (diff) | |
| parent | 362879d8c13f3912510c5a299dbf6fa2c2067afa (diff) | |
| download | rust-38eaf608eb9e0dddda1de1e03b08be123450e9b6.tar.gz rust-38eaf608eb9e0dddda1de1e03b08be123450e9b6.zip | |
Rollup merge of #131707 - clarfonthey:constify-core-tests, r=thomcc
Run most `core::num` tests in const context too This adds some infrastructure for something I was going to use in #131566, but it felt worthwhile enough on its own to merge/discuss separately. Essentially, right now we tend to rely on UI tests to ensure that things work in const context, rather than just using library tests. This uses a few simple macro tricks to make it *relatively* painless to execute tests in both runtime and compile-time context. And this only applies to the numeric tests, and not anything else. Recommended to review without whitespace in the diff. cc `@RalfJung`
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/mod.rs')
0 files changed, 0 insertions, 0 deletions