This bugzilla service is closed. All entries have been migrated to https://gitlab.com/libeigen/eigen
Bug 1532 - C++17 STL warnings: deprecated std::unary_negate and std::binary_negate
Summary: C++17 STL warnings: deprecated std::unary_negate and std::binary_negate
Status: RESOLVED FIXED
Alias: None
Product: Eigen
Classification: Unclassified
Component: Core - general (show other bugs)
Version: 3.3 (current stable)
Hardware: All All
: Normal Unknown
Assignee: Nobody
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-27 18:26 UTC by patrikhuber
Modified: 2019-12-04 17:34 UTC (History)
3 users (show)



Attachments

Description patrikhuber 2018-03-27 18:26:20 UTC
std::unary_negate and std::binary_negate have been deprecated in C++17. VS2017 gives the following compiler warnings when compiled in C++17 mode (/std:c++17):

1>c:\users\patrik\vcpkg\installed\x64-windows\include\eigen\src\core\functors\stlfunctors.h(87): warning C4996: 'std::unary_negate<_Fn>': warning STL4008: std::not1(), std::not2(), std::unary_negate, and std::binary_negate are deprecated in C++17. They are superseded by std::not_fn(). You can define _SILENCE_CXX17_NEGATORS_DEPRECATION_WARNING or _SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have received this warning.

1>c:\users\patrik\vcpkg\installed\x64-windows\include\eigen\src\core\functors\stlfunctors.h(91): warning C4996: 'std::binary_negate<_Fn>': warning STL4008: std::not1(), std::not2(), std::unary_negate, and std::binary_negate are deprecated in C++17. They are superseded by std::not_fn(). You can define _SILENCE_CXX17_NEGATORS_DEPRECATION_WARNING or _SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have received this warning.

I think it would be really nice to update this code to make Eigen warnings-free again.
Comment 2 Nobody 2019-12-04 17:34:24 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/1532.

Note You need to log in before you can comment on or make changes to this bug.