Ronny Bergmann

How would that work? I would have to know whether the manifold has arrays or bits and depending on that initialise the fields differently as well as update them differently?...

The evaluation type is used for distinguishing `grad_f(M,p)` and `grad_f!(M, X, p)` in the function handles :) I still do not understand what you mean. I want the user to...

No my main problem is any points/vectors that are not arrays but floats. Unless I overwrite the store command for these and `Ref`any float?

So I would `Ref(...)`all my fields? Doesn't‘t that destroy the advantages again?

Hm, sounds strange to me and seems a little hustle to implement it that way, what if the default is to not Ref – but have the special cases (I...

that sounds like a good idea :) Will try that as my next feature (ehem, well after Frank Wolfe and Times)

Ah it might be a little more tricky, since for example storing the cost (because evaluation it again might be too expensive) is probably a float independent of the manifold,...

Thanks for the input. Indeed while the Tuple is used during the iterations to store “stuff” its types do not change (usually just the stored values in the arrays/ `Ref`ed...

For me it seems that this might for now be too much effort in implementation compared to the gain? At least for now it seems it to me might be...

No, this one. CostGrad should be quite easy, just also providing an easy interface might be a little work.