-
Notifications
You must be signed in to change notification settings - Fork 64
fix #685 #688
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
fix #685 #688
Conversation
|
Tests pass locally. CI failure seems unrelated to this PR, and is due to CI using deprecated actions. To fix that, please consider merging the Dependabot PRs. |
|
Integration tests are also failing for #693, which suggests that is unrelated to the fix introduced in this PR. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #688 +/- ##
==========================================
+ Coverage 93.44% 93.46% +0.01%
==========================================
Files 14 14
Lines 992 994 +2
==========================================
+ Hits 927 929 +2
Misses 65 65 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Friendly bump. |
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.
I think currently tests don't cover all changes in the PR: #688 (comment)
This seems to be confirmed by the code coverage analysis: https://app.codecov.io/gh/JuliaDiff/ChainRulesCore.jl/pull/688?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=JuliaDiff
|
While it doesn't hit the one for AbstractThunk, the code is right. |
|
I added a test: it = InplaceableThunk(x -> x + [1], @thunk [1.0])
@test ProjectTo(BitArray([0]))(it) == NoTangent()But that still gave an ambiguity error. So I replaced: (::ProjectTo{NoTangent})(::AbstractThunk) = NoTangent()with (::ProjectTo{NoTangent})(::InplaceableThunk) = NoTangent()which solves the issue. And now both method definitions are hit by the tests. |
|
Could we tag release with this? If so, should I bump the version in this PR? |
|
Yes, good point, please go ahead and update the version number in this PR. |
Done. |
Attempt to fix #685