-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add iszero(x)
branches to xlogy
and xlog1py
#85
Conversation
Codecov Report
@@ Coverage Diff @@
## master #85 +/- ##
=======================================
Coverage 97.00% 97.00%
=======================================
Files 3 3
Lines 167 167
=======================================
Hits 162 162
Misses 5 5
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Co-authored-by: David Widmann <[email protected]>
Co-authored-by: David Widmann <[email protected]>
The failures in Nabla.jl and EAGO.jl seem unrelated to this PR. |
Is this fine to be merged? |
I'm bumping this as it is still unclear to me what if anything is missing. |
Then I think we can merge and I'll change JuliaStats/LogExpFunctions.jl#54 to follow the same guidelines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK. We want to use the same rules in LogExpFunctions. Unfortunately, currently these rules cause test failures: JuliaStats/LogExpFunctions.jl#57 So let us wait with this PR until we have solved these issues in LogExpFunctions, in case we have to handle some other special case here.
This should be fine to be merged now as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test failures are unrelated, see FluxML/Tracker.jl#125. Similar issues seem to exist for ReverseDiff on Julia 1.8.
Can we add some tests of the new branches though?
Sure. I just don't know where to put them, since there currently do not seem to be any tests for EDIT: or should new branches be created under the |
All rules apart from the ones excluded in Line 17 in 2c29d7d
Lines 19 to 110 in 2c29d7d
Tests of such special cases might be best to add below Line 142 in 2c29d7d
rem2pi and ldexp .
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks!
The test failure is a downstream issue in ReverseDiff that's also present on the master branch and in ReverseDiff's CI.
It is unclear to me how the tests work here. I did not find the tests of corner cases.