-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
Relax type constraints to allow callable parameters in pdeps #3079
Conversation
I'm having some trouble with the test. The codegen doesn't seem to do the replacement of the parameter in
|
You probably need to |
2526813
to
89886a0
Compare
Thanks! That fixed it. |
89886a0
to
6f96622
Compare
@ChrisRackauckas test failures seem the same as master. Does this look okay? |
I don't like that they are just relaxed, but if @AayushSabharwal thinks it's required then let's go with it. |
What would be the alternative? I understand that we don't want to introduce type parameters (to avoid increasing inference time?). |
What's not to like? 😅 Looks good to me, and a fairly simple change allows new features. |
lost a validation step, but if it's required, sure. |
Checklist
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
Additional context
Currently parameter dependencies assume that we only have
BasicSymbolic
. I tried to relax that constraint a bit to allow callable parameters to be stored too. If one has both callable parameters and normal ones in the parameter dependencies, I think that there might be a performance issue, but otherwise it should not affect nortmal usage.@AayushSabharwal is this the right way of handling this issue? I think that for normal parametrs we store things in the non-numeric portion and that's splitted by types (?), so that might be better for the heterogenuous case.