bob.math.linsolve parameter documentation in inconsistent order
Created by: siebenkopf
I just saw that the documented order of the parameters of
bob.math.linsolve (and similar) is not the same as they are actually used:
I think we should actually change the bindings, so that the parameters are actually as currently documented and not as currently used. This is the default way that we use in other packages as well, i.e., the optional output value should go last in the list of parameters, for example:
If not desired otherwise, I will update the code accordingly.
Also, I have seen that we are binding
linsolve_) functions, while in the other packages we removed the bindings for those. At the end, in the binding functions, in fact we are checking the parameters, even in the
nocheck functions. Finally, the test does not take a lot of time, so the gain is not big. And, having no checks might result in crashes (SIGSEGV), which should be avoided in Python code.
So, if there are no objections, I will remove the bindings to those functions as well.
Both modifications will end up in an API change, so we get new version