Is there any reason that there is no concrete version of math operation on, say DenseReal64Vector ?

[keitamasuda]

On the doc, it says

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?

[pbenner]

You're right, there is no reason. I will add the missing methods.

[pbenner]

Done

[keitamasuda]

@pbenner
Thank you!
I thought there was a deep technical difficulty or design issue for this matter (that wasn't the case).