rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Use CheckCtx in more places

Browse Source 
Rather than passing names or identifiers, just pass `CheckCtx` in a few
more places.
This commit is contained in:
Trevor Gross
2024-12-26 07:42:13 +00:00
parent 86aeee818b
commit 7082f9baf7
4 changed files with 17 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
library/compiler-builtins/libm/crates/libm-test/src/gen/domain_logspace.rs
View File

@@ -4,7 +4,7 @@ use libm::support::{IntTy, MinInt};
use crate::domain::HasDomain;
use crate::op::OpITy;
use crate::{MathOp, logspace};
use crate::{CheckCtx, MathOp, logspace};
/// Number of tests to run.
// FIXME(ntests): replace this with a more logical algorithm
@@ -30,7 +30,7 @@ const NTESTS: usize = {
///
/// This allows us to get reasonably thorough coverage without wasting time on values that are
/// NaN or out of range. Random tests will still cover values that are excluded here.
pub fn get_test_cases<Op>() -> impl Iterator<Item = (Op::FTy,)>
pub fn get_test_cases<Op>(_ctx: &CheckCtx) -> impl Iterator<Item = (Op::FTy,)>
where
Op: MathOp + HasDomain<Op::FTy>,
IntTy<Op::FTy>: TryFrom<usize>,

4
library/compiler-builtins/libm/crates/libm-test/src/gen/edge_cases.rs
View File

@@ -3,7 +3,7 @@
use libm::support::Float;
use crate::domain::HasDomain;
use crate::{FloatExt, MathOp};
use crate::{CheckCtx, FloatExt, MathOp};
/// Number of values near an interesting point to check.
// FIXME(ntests): replace this with a more logical algorithm
@@ -14,7 +14,7 @@ const AROUND: usize = 100;
const MAX_CHECK_POINTS: usize = 10;
/// Create a list of values around interesting points (infinities, zeroes, NaNs).
pub fn get_test_cases<Op, F>() -> impl Iterator<Item = (F,)>
pub fn get_test_cases<Op, F>(_ctx: &CheckCtx) -> impl Iterator<Item = (F,)>
where
Op: MathOp<FTy = F> + HasDomain<F>,
F: Float,