Skip to content
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

Tighten WoodburyPDMat signature #81

Merged
merged 4 commits into from
Aug 3, 2022
Merged

Tighten WoodburyPDMat signature #81

merged 4 commits into from
Aug 3, 2022

Conversation

dkarrasch
Copy link
Contributor

This came up in a nanosoldier run in JuliaLang/julia#46196. The proposed change should not alter the current behaviour and should be backward compatible, but additionally should make this package "ready" for JuliaLang/julia#46196 in case it gets accepted.

@codecov
Copy link

codecov bot commented Jul 31, 2022

Codecov Report

Merging #81 (838c21a) into main (6d15d47) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #81   +/-   ##
=======================================
  Coverage   92.95%   92.95%           
=======================================
  Files          13       13           
  Lines         525      525           
=======================================
  Hits          488      488           
  Misses         37       37           
Impacted Files Coverage Δ
src/woodbury.jl 100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@sethaxen
Copy link
Member

sethaxen commented Aug 2, 2022

Thanks for the PR! My only concern is whether there are some invocations of qr whose Q is not an AbstractQ. e.g. for some overload for a user-defined matrix. This really isn't an issue for this package, but it is if we upstream this structure to PDMatsExtras as is planned.

The alternative to narrowing the type would be widening, i.e. removing type constraints. What do you think?

@dkarrasch
Copy link
Contributor Author

Yes, that's another option. I was not aware of any context. Widening is perhaps even the better idea for generic programming.

@sethaxen
Copy link
Member

sethaxen commented Aug 3, 2022

Let's go with widened then. Thanks for the PR!

@sethaxen sethaxen merged commit cbb8c91 into mlcolab:main Aug 3, 2022
@dkarrasch dkarrasch deleted the patch-1 branch August 3, 2022 10:27
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