Re: [eigen] Custom expression type API stability

[ Thread Index | Date Index | More Archives ]

Indeed, writing custom expressions still requires to play with Eigen::internal, meaning that it is subject to change in the future. As you noticed, the current 3.2 way is different than the future 3.3 way. If you tell us a bit more about your need for a custom _expression_ we might be able to guide you towards the best approach. Maybe you don't need a new one at all, maybe ReturnByValue if good for, etc.


On Thu, Feb 18, 2016 at 11:06 AM, Dan Čermák <dan.cermak@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Folks,

I have a question concerning adding custom _expression_ types as described here: . I am
currently developing a program that would require some custom _expression_ types
to be efficient.
Is the way how they are implemented expected to change during the next
versions? Since I could not compile the example with Eigen 3.2.7 and 3.2.8,
only with the latest snapshot from mercurial.



Mail converted by MHonArc 2.6.19+