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
Methods, such as VaddV and MaddM, are generic and accept vector or matrix types that implement the respective ConstVector or ConstMatrix interface.
However, opertions on interface types are much slower than on concrete types, which is why most vector and matrix types in autodiff also implement methods that operate on concrete types.
For instance, DenseFloat64Vector implements a method called VADDV that takes as arguments two objects of type DenseFloat64Vector.
Methods that operate on concrete types are always named in capital letters.
But many types doesn't have the concrete version of the method. DenseReal64 is one of those type where it has MdotV but no MDOTV.
Is there any reason for this?
The text was updated successfully, but these errors were encountered:
On the doc, it says
But many types doesn't have the concrete version of the method.
DenseReal64
is one of those type where it hasMdotV
but noMDOTV
.Is there any reason for this?
The text was updated successfully, but these errors were encountered: