Subject: Re: [boost] [Hana/Fit] about constexpr/noexcept on equivalent functions to std::overload
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2016-07-08 01:54:23
Le 02/07/2016 Ã 19:53, Paul Fultz II a Ã©crit :
>> On Jul 2, 2016, at 3:03 AM, Vicente J. Botet Escriba <vicente.botet_at_[hidden]> wrote:
>> On the C++ standard meating in Oulu, we decided to make the std::overload function constexpr and conditionaly noexcept and ensure that the overloaded functions shall be constexpr if the stored finctions are.
>> I don't find in the reference documentation of Hana and Fit any reference of whether the overloaded functions preserve constexpr or not.
>> There is a reedit post  and CWG issue 1581  that are related.
>> Could the authors clarify?
> The Fit library preserves constexpr both for initialization of the function and the evaluation of the function. However, the evaluation of constexpr functions are somewhat limited on gcc 4.6 and MSVC due to bugs in their implementations,
Have these bugs been fixed?
> however, constexpr initialization is supported. This is described here in the documentation:
> Note, constexpr does make the instantiations of templates more aggressive since it will instantiate the body of the constexpr function, however, this is not a problem if the function is properly constrained.
What do you mean by properly constrained?
> All the functions in the Fit library are SFINAE-friendly, which help preserve the constraints of functions after being adapted.
Could you elaborate with some examples?
> Constexpr does become an issue for the fix-point combinator because it wonât stop instantiating due to recursion. Instead, the Fit library has a depth it uses to stop the constexpr instantiation. That is, the overloads are declared constexpr up to a certain depth and then switches to overloads that are not constexpr. This depth can be set by FIT_RECURSIVE_CONSTEXPR_DEPTH macro(defaults to 16), see here:
> There is no support for noexcept currently in the Fit library. I have thought about adding support for it at some point. I have heard for some people that it wasnât necessary. The difficult problem with noexcept is that it doesnât take part in the substitution failure, so some care needs to be taken that substitution failure happens before the noexcept clause is evaluated. Since the committee is adding noexcept to adaptors such as `std::overload`, I think it would be good idea to add that to the Fit library as well.
Is this something the compiler must fix?
Could you tell me more about how would you avoid the substitution
failure inside noexcept?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk