diff options
| author | bors <bors@rust-lang.org> | 2023-11-18 08:49:03 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-18 08:49:03 +0000 |
| commit | 6416e2e675504abc924592452e5f6874fdddb0dd (patch) | |
| tree | 73b63798570e86105a940552a4b81e4f2e0fc493 /compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp | |
| parent | 61d3b263a793b390f6231f08d862e8c71d04e3ef (diff) | |
| parent | 8066079b5bc2f5d1ba09f389575957a9113e029a (diff) | |
| download | rust-6416e2e675504abc924592452e5f6874fdddb0dd.tar.gz rust-6416e2e675504abc924592452e5f6874fdddb0dd.zip | |
Auto merge of #115412 - eswartz:docs/total_cmp-test-result-in-docs, r=scottmcm
Expose tests for {f32,f64}.total_cmp in docs
Expose tests for {f32,f64}.total_cmp in docs
Uncomment the helpful `assert_eq!` line, which is stripped out completely in docs, and leaves the reader to mentally play through the algorithm, or go to the playground and add a println!, to see what the result will be.
(If these tests are known to fail on some platforms, is there some mechanism to conditionalize this or escape the test so the `assert_eq!` source will be visible on the web? I am a newbie, which is why I was reading docs ;)
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp')
0 files changed, 0 insertions, 0 deletions