Repository navigation
The integrator and evaluation probe with EvalNumerical and catch CannotEvalException #1543
Description
EvalNumerical throws CannotEvalException by contract, and several places call it only to catch that and read it as "no value here": PartialFractions.HoldsAtSampledPoints (gone in #1497), IndefiniteIntegralSolver at four sites (two of them wrapping a call that already catches it), Limits/Transformations.cs and IndefiniteIntegralSolver.cs:215 behind catch (Exception), and Minimiser with EvalBoolean. Evaled is Number.Complex (and is Boolean) is the non-throwing form. Part of #1540.
Activity
Probes read Evaled instead of catching EvalNumerical's exception (#1553)
Happypig375 commentedon Sep 29, 2026
This will be improved with v3 such that a lack of value is null instead of exception
Rafael-SOWNet commentedon Sep 29, 2026
Queued as #1570 (3.0, under #1540). Until then, what remains here is the one catch in
HoldsAtSampledPoints, which #1497 replaces with interval evaluation; #1553 took the rest.The integrator's sampled-point checks evaluate in intervals, which re…