You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FinDate has been implemented with only some Python datetime dependency in a few functions.
However the issue of processing speed is becoming more important.
I would be interested to know which of the following approaches is superior in speed terms.
Make FinDate (which now includes date and time) a thin layer over datetime i.e. all functions should call datetime functions rather than do processing themselves.
or
Make FinDate independent of datetime and do all of the logic in the FinDate class. In this case consider if FinDate should be sped up using numba ? Functions like addDays and addMonths might benefit.
I imagine two implementations of FinDate which can be implemented and compared. Only core functions of date generation and differencing and rolling foward in date steps should be compared as most other functions build on these.
The text was updated successfully, but these errors were encountered:
FinDate has been implemented with only some Python datetime dependency in a few functions.
However the issue of processing speed is becoming more important.
I would be interested to know which of the following approaches is superior in speed terms.
or
I imagine two implementations of FinDate which can be implemented and compared. Only core functions of date generation and differencing and rolling foward in date steps should be compared as most other functions build on these.
The text was updated successfully, but these errors were encountered: