Kai Striega

@garfieldthecat I'm sorry that no one has taken the time to look at this. I've started doing some maintenance work on numpy-financial and have also noticed the speed to be...

> 1. part of the reason why all the functions are very slow seems to be the fact that they are set up to accept both scalars and arrays as...

This could be a good idea. The exiting split/index implementations does become convoluted especially, as you have already said, for functions with multiple edge cases. I'm not familiar enough with...

@charris could I ask for your opinion on this? Personally, I agree with @person142 that the current approach (“split the array up using Boolean indexes and then do different things...

With regard to the scope, ideally we'd be able to determine what the people actually using the financial functions will actually use. Even if we were to add more functions,...

> I do not know if it's your first experience with Cython It's not my *first* time, but I am still very inexperienced. Any help is appreciated :) > I...

Sorry that this is taking so long. I'm having some trouble cythonizing ``find_interval_ascending``. What I'm having trouble with is that `grid` seems to a list of either doubles or longs,...

> Can you push the attempt which shows the error? @ev-br done. I've also added a few comments

@ev-br I think it's time for you to take another look. I've rebased it onto the newer changes in main, and gotten it to run for all tests except for...

> Are there any realistic enough input variables that I can play with to ``evaluate_linear`` and to ``find_interval_ascending``? I've been using the benchmarks to test against. I think you should...