Re: [eigen] Noexcept move assignment and construction

[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]

To: eigen <eigen@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [eigen] Noexcept move assignment and construction
From: Gael Guennebaud <gael.guennebaud@xxxxxxxxx>
Date: Tue, 29 Mar 2016 23:03:52 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=AOoPgsBQLGP/+1dNH1VHq8lPznTR9nsCqbug3aKtOnY=; b=bUvdTIbtE8fNXJgm/g0ayYaw2NvTgUI9Mxqc66Bmyy0Yc9MqQRKYD8CMjlXe1+MrGa 3VLFXkxKQ1f57yuIa1lKkO9UKYRyzrxH9A5i6FHy7Ys3ZQ3LIOAGVEieUrhDrMez7Afb J5T//OubiVLd1Fc+BnMMm6isFxwvSr37LYlwapxIbPsyf+rqIU0WIQbjVasryrHUihwy b2oXGqoTY2xLM6wh4dR8eaCUhuquj3q/5Nrrh3Ns9TxlmvaVh6ezkamd03Cl5URm75E0 E/Fw5mYevgeAHsBmZQkKv8CUj9hmJ0riuUyIJFnafxKhOFMDFQuwzlhplYXPdyhzCcO5 sy1Q==

We definitely have to fix this issue. Let's continue of the respective bug entry.

gael

On Tue, Mar 29, 2016 at 7:30 PM, Breannan Smith <smithbreannan@xxxxxxxxx> wrote:

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

[1] http://eigen.tuxfamily.org/bz/show_bug.cgi?id=725

References:
- [eigen] Noexcept move assignment and construction
  - From: Breannan Smith

Messages sorted by: [ date | thread ]
Prev by Date: Re: [eigen] Problem with fft and custom allocator
Next by Date: [eigen] unsubscribe
Previous by thread: [eigen] Noexcept move assignment and construction
Next by thread: [eigen] Using Matrix<AutoDiff> in conjunction with Matrix<double>?

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/