Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why is `std::invoke` not constexpr?

Shouldn't std::invoke be constexpr especially after constexpr lambdas in C++17?

Are there any obstacles that will prevent this?

like image 860
Vahagn Avatar asked Oct 24 '16 16:10

Vahagn


1 Answers

Update: P1065 will make it constexpr.


Keep original post for historical reason:

From the proposal:

Although there is possibility to implement standard conforming invoke function template as a constexpr function, the proposed wording does not require such implementation. The main reason is to left it consistent with existing standard function objects, that could have such definition, like std::mem_fn, std::reference_wrapper and operator wrappers. Furthermore imposing such requirement will block the implementation of invoke that refers to std::mem_fn.

This proposal assumes that constexpr addition to the header would be applied consistently by a separate proposal.

Both constexpr and standard library based implementation are presented in Implementability section of the proposal.


Related CWG issue #1581: When are constexpr member functions defined?.

like image 127
Vittorio Romeo Avatar answered Oct 17 '22 01:10

Vittorio Romeo