forked from SciML/ODE.jl
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Duck typing and consistent return types (Vector{typeof(y0)}) for all …
…solvers; see SciML#7. Tests adjusted accordingly.
- Loading branch information
Showing
2 changed files
with
59 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While we're changing this, maybe it would make sense to
s/x0/y0
here as well, to have consistent argument naming across all the methods. Since it's not uncommon to talk about eitherx = f(t)
,y = f(x)
ory = f(t)
, (or eveny = f(t,x)
I think calling the solutiony
is the least ambiguous -y
is almost always used as whateverf
is describing, andt
is almost always used as the (/an) argument tof
, whilex
can be either.