Skip to content

Conversation

devmotion
Copy link
Member

@devmotion devmotion requested a review from giordano October 3, 2025 12:35
Copy link

codecov bot commented Oct 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.97%. Comparing base (1f0527c) to head (148041f).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #504      +/-   ##
==========================================
- Coverage   94.11%   93.97%   -0.14%     
==========================================
  Files          14       14              
  Lines        2905     2904       -1     
==========================================
- Hits         2734     2729       -5     
- Misses        171      175       +4     
Flag Coverage Δ
unittests 93.97% <100.00%> (-0.14%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment on lines -122 to -129
# In future just use `fastabs` from Base.Math
# https://github.com/JuliaLang/julia/blob/93fb785831dcfcc442f82fab8746f0244c5274ae/base/special/trig.jl#L1057
if isdefined(Base.Math, :fastabs)
import Base.Math: fastabs
else
fastabs(x::Number) = abs(x)
fastabs(x::Complex) = abs(real(x)) + abs(imag(x))
end
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since fastabs is technically not public, maybe it's safer to keep this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm... maybe. Codecov was complaining (correctly) that these lines are not covered by tests anymore. So in that sense technically the fallback is not safe either as it's untested when dropping support for Julia < 1.10.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the better approach would be to mark Base.Math.fastabs as public?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but good luck with that 😅

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apart from making Base.Math.fastabs public, the only other "correct" approach would be to only define it in SpecialFunctions, ie to only keep the second branch. Then we would neither rely on internals nor on untested code.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe that's not too bad, it's two very simple methods, and unlikely to need maintenance.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I removed the first branch 🙂

@devmotion devmotion requested a review from giordano October 3, 2025 18:20
@devmotion devmotion merged commit fddf5e0 into master Oct 3, 2025
11 of 12 checks passed
@devmotion devmotion deleted the dw/julia_compat branch October 3, 2025 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants