I have a few classes with potentially noexcept default move assignment operators and move constructors, but it seems that Eigen's move operations are *not* noexcept, which precludes their use in noexcept contexts. Is this an intentional design decision or just an oversight? The only reference I could find to this issue is a two year old bug report [1].
Thanks!
Best regards,
Breannan Smith