[type_traits] Some traits are missing
Hi all, Equivalents of following traits are in C++11 Standard, but missing in Boost.TypeTraits library: has_nothrow_move_assign has_nothrow_move_constructor has_trivial_move_assign has_trivial_move_constructor Extremely naive implementation of those functions exist in Boost.Variant, so as a start we can use them. Or am I missing something and there is a reason, why those traits are not included in Boost.TypeTraits? -- Best regards, Antony Polukhin
Equivalents of following traits are in C++11 Standard, but missing in Boost.TypeTraits library:
has_nothrow_move_assign has_nothrow_move_constructor has_trivial_move_assign has_trivial_move_constructor
Extremely naive implementation of those functions exist in Boost.Variant, so as a start we can use them.
Or am I missing something and there is a reason, why those traits are not included in Boost.TypeTraits?
New traits are normally only added when someone offers to do the work... so if you're offering ;-) John.
Equivalents of following traits are in C++11 Standard, but missing in Boost.TypeTraits library:
has_nothrow_move_assign has_nothrow_move_constructor has_trivial_move_assign has_trivial_move_constructor
Or am I missing something and there is a reason, why those traits are not included in Boost.TypeTraits?
New traits are normally only added when someone offers to do the work... so if you're offering ;-)
In the same vein, I noticed two days ago that type trait boost::conditional is present when including "boost/type_traits/conditional.hpp" (but not defined by boost/type_traits.hpp) and thus std::tr1::conditional is not defined when including "boost/tr1/type_traits.hpp" After some searching, it turns out that 'conditional' was not part of TR1 (that explains the above) but that it was added with N2240 to the C++ 2011 standard: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2240.html Hence my question, should 'conditional' (and probably 'enable_if') be added to "boost/tr1/type_traits.hpp" ? Regards, Étienne This message and any attachments are confidential and intended solely for the addressees. Any unauthorized modification, edition, use or dissemination is prohibited. If you have received this message by mistake, please notify us immediately. ATEME decline all responsibility for this message if it has been altered, deformed, falsified or even edited or disseminated without authorization.
After some searching, it turns out that 'conditional' was not part of TR1 (that explains the above) but that it was added with N2240 to the C++ 2011
standard: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2240.html
Hence my question, should 'conditional' (and probably 'enable_if') be added to "boost/tr1/type_traits.hpp" ?
No, that header is frozen at the TR1 features, it should be in boost/type_traits.hpp though - can you open a bug report on that so I don't forget? Thanks, John.
After some searching, it turns out that 'conditional' was not part of TR1 (that explains the above) but that it was added with N2240 to the C++ 2011
standard: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2240.html
Hence my question, should 'conditional' (and probably 'enable_if') be added to "boost/tr1/type_traits.hpp" ?
No, that header is frozen at the TR1 features, it should be in boost/type_traits.hpp though - can you open a bug report on that so I don't forget?
Done: https://svn.boost.org/trac/boost/ticket/8188 This is a very minor issue, I was just puzzled not to find 'conditional' where I expected it to be. Regards, Étienne This message and any attachments are confidential and intended solely for the addressees. Any unauthorized modification, edition, use or dissemination is prohibited. If you have received this message by mistake, please notify us immediately. ATEME decline all responsibility for this message if it has been altered, deformed, falsified or even edited or disseminated without authorization.
2013/2/27 John Maddock <boost.regex@virgin.net>:
New traits are normally only added when someone offers to do the work... so if you're offering ;-)
I've created ticket https://svn.boost.org/trac/boost/ticket/8189 I can take care of it, so may I commit to trunk to type_triats directly? -- Best regards, Antony Polukhin
New traits are normally only added when someone offers to do the work... so if you're offering ;-)
I've created ticket https://svn.boost.org/trac/boost/ticket/8189 I can take care of it, so may I commit to trunk to type_triats directly?
OK sure, go for it. Thanks, John.
2013/2/28 John Maddock <boost.regex@virgin.net>:
I've created ticket https://svn.boost.org/trac/boost/ticket/8189 I can take care of it, so may I commit to trunk to type_triats directly?
OK sure, go for it.
All the regression tests passed well, documentation updated. Boost.Variant was moved to new type trait and works well (not committed to trunk yet). If all the changes are OK, please merge type traits it to release branch and close #8189. -- Best regards, Antony Polukhin
I've created ticket https://svn.boost.org/trac/boost/ticket/8189 I can take care of it, so may I commit to trunk to type_triats directly?
OK sure, go for it.
All the regression tests passed well, documentation updated. Boost.Variant was moved to new type trait and works well (not committed to trunk yet).
If all the changes are OK, please merge type traits it to release branch and close #8189.
Looks good, there appear to be a few vc-11 failures, which I've just committed a tentative fix for, so I'll let the tests cycle one at least more time before merging to release. John.
2013/3/15 John Maddock <boost.regex@virgin.net>:
there appear to be a few vc-11 failures, which I've just committed a tentative fix for, so I'll let the tests cycle one at least more time before merging to release.
Those are old tests from March 2, I've already fixed that issue in https://svn.boost.org/trac/boost/changeset/83245 and it is not reproduced any more (there are some newer tests on vc11 and they pass well). -- Best regards, Antony Polukhin
participants (3)
-
Antony Polukhin -
DUPUIS Etienne -
John Maddock