coretests: move float tests from num to floats module and use a more flexible macro to generate them#141857
Merged
bors merged 1 commit intorust-lang:masterfrom Jun 7, 2025
Merged
Conversation
Collaborator
|
rustbot has assigned @Mark-Simulacrum. Use |
Member
Author
|
r? @tgross35 |
This comment has been minimized.
This comment has been minimized.
77b3d3d to
f3b4668
Compare
This comment has been minimized.
This comment has been minimized.
tgross35
reviewed
Jun 3, 2025
Contributor
tgross35
left a comment
There was a problem hiding this comment.
Thanks for putting this together, I really like the way it turned out. Just a nit suggesting an example in the docs and optionally removing cfg(bootstrap). r=me after that and green CI (assuming the failure is unrelated)
0c707f9 to
fdadc1c
Compare
This comment has been minimized.
This comment has been minimized.
Member
Author
|
That test is kind of silly inside coretests... |
fdadc1c to
bc0b999
Compare
tgross35
reviewed
Jun 3, 2025
tgross35
approved these changes
Jun 3, 2025
bc0b999 to
d296c12
Compare
Member
Author
|
@bors r=tgross35 |
Collaborator
Collaborator
|
☔ The latest upstream changes (presumably #141984) made this pull request unmergeable. Please resolve the merge conflicts. |
d296c12 to
ccf9a89
Compare
Member
Author
|
@bors r=tgross35 |
Collaborator
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this pull request
Jun 4, 2025
coretests: move float tests from num to floats module and use a more flexible macro to generate them This makes some progress on rust-lang#141726 by moving the float tests in `num` to `floats` and using a newer, more flexible macro to generate them. We also newly run these tests on f16 and f128 in const, and at runtime in Miri and for hosts where that works well enough. I didn't yet deduplicate any tests or port the existing `floats::f*` tests to the macro, that can happen in a future PR.
bors
added a commit
that referenced
this pull request
Jun 4, 2025
Rollup of 9 pull requests Successful merges: - #141271 (Streamline some attr parsing APIs) - #141570 (Fix incorrect eq_unspanned in TokenStream) - #141857 (coretests: move float tests from num to floats module and use a more flexible macro to generate them) - #141893 (remove `f16: From<u16>`) - #141924 (Lightly tweak docs for BTree{Map,Set}::extract_if) - #141939 (exact_div: add tests) - #141959 (Add more missing 2015 edition directives) - #142002 (redesign stage 0 std follow-ups part2) - #142007 (Improve some `Visitor` comments.) r? `@ghost` `@rustbot` modify labels: rollup
Member
…flexible macro to generate them
ccf9a89 to
7742d0e
Compare
Member
Author
|
@bors2 try |
Contributor
rust-bors bot
added a commit
that referenced
this pull request
Jun 4, 2025
coretests: move float tests from num to floats module and use a more flexible macro to generate them This makes some progress on #141726 by moving the float tests in `num` to `floats` and using a newer, more flexible macro to generate them. We also newly run these tests on f16 and f128 in const, and at runtime in Miri and for hosts where that works well enough. I didn't yet deduplicate any tests or port the existing `floats::f*` tests to the macro, that can happen in a future PR. <!-- homu-ignore:start --> <!-- If this PR is related to an unstable feature or an otherwise tracked effort, please link to the relevant tracking issue here. If you don't know of a related tracking issue or there are none, feel free to ignore this. This PR will get automatically assigned to a reviewer. In case you would like a specific user to review your work, you can assign it to them by using r? <reviewer name> --> <!-- homu-ignore:end --> try-job: x86_64-gnu-aux
Contributor
Member
Author
|
@bors r=tgross35
|
Collaborator
jhpratt
added a commit
to jhpratt/rust
that referenced
this pull request
Jun 7, 2025
coretests: move float tests from num to floats module and use a more flexible macro to generate them This makes some progress on rust-lang#141726 by moving the float tests in `num` to `floats` and using a newer, more flexible macro to generate them. We also newly run these tests on f16 and f128 in const, and at runtime in Miri and for hosts where that works well enough. I didn't yet deduplicate any tests or port the existing `floats::f*` tests to the macro, that can happen in a future PR. try-job: x86_64-gnu-aux
This was referenced Jun 7, 2025
bors
added a commit
that referenced
this pull request
Jun 7, 2025
Rollup of 8 pull requests Successful merges: - #137992 (Stabilise `os_string_pathbuf_leak`) - #141558 (Limit the size of cgu names when using the `-Zhuman-readable-cgu-name…) - #141797 (compiler: set Apple frame pointers by architecture) - #141857 (coretests: move float tests from num to floats module and use a more flexible macro to generate them) - #142045 (Make obligation cause code suggestions verbose) - #142076 (Check documentation of bootstrap in PR CI) - #142110 (Add solaris targets to build-manifest) - #142131 (Make cast suggestions verbose) r? `@ghost` `@rustbot` modify labels: rollup
rust-timer
added a commit
that referenced
this pull request
Jun 7, 2025
Rollup merge of #141857 - RalfJung:coretests-floats, r=tgross35 coretests: move float tests from num to floats module and use a more flexible macro to generate them This makes some progress on #141726 by moving the float tests in `num` to `floats` and using a newer, more flexible macro to generate them. We also newly run these tests on f16 and f128 in const, and at runtime in Miri and for hosts where that works well enough. I didn't yet deduplicate any tests or port the existing `floats::f*` tests to the macro, that can happen in a future PR. try-job: x86_64-gnu-aux
tautschnig
pushed a commit
to model-checking/verify-rust-std
that referenced
this pull request
Jun 17, 2025
coretests: move float tests from num to floats module and use a more flexible macro to generate them This makes some progress on rust-lang#141726 by moving the float tests in `num` to `floats` and using a newer, more flexible macro to generate them. We also newly run these tests on f16 and f128 in const, and at runtime in Miri and for hosts where that works well enough. I didn't yet deduplicate any tests or port the existing `floats::f*` tests to the macro, that can happen in a future PR. try-job: x86_64-gnu-aux
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This makes some progress on #141726 by moving the float tests in
numtofloatsand using a newer, more flexible macro to generate them. We also newly run these tests on f16 and f128 in const, and at runtime in Miri and for hosts where that works well enough.I didn't yet deduplicate any tests or port the existing
floats::f*tests to the macro, that can happen in a future PR.try-job: x86_64-gnu-aux