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
In a recent Discourse thread it surfaced that get_nargs takes up a sizeable part of the benchmark. The reason is that it allocates the whole methods table before considering the first element:
get_nargs(f) =first(methods(f)).nargs -1
Besides it is not necessarily accurate if several methods have varying numbers of arguments. Any idea how we could overcome this?
The text was updated successfully, but these errors were encountered:
Sorry for the slow reply here. The obvious workaround would be for nargs to be an input to the constructor. Or we could have two constructors, LinearOperator and LinearOperator5 (say) for products with 5 arguments.
Sorry for the slow reply here. The obvious workaround would be for nargs to be an input to the constructor. Or we could have two constructors, LinearOperator and LinearOperator5 (say) for products with 5 arguments.
In a recent Discourse thread it surfaced that
get_nargs
takes up a sizeable part of the benchmark. The reason is that it allocates the whole methods table before considering the first element:Besides it is not necessarily accurate if several methods have varying numbers of arguments. Any idea how we could overcome this?
The text was updated successfully, but these errors were encountered: