[Bug c++/86282] Evaluation order in if constexpr expression seems to be irrelevant for evaluating type traits

2018-06-22 Thread rene.r...@fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86282 --- Comment #5 from rene.r...@fu-berlin.de --- Many thanks for the explanation and the code examples.

[Bug c++/86282] Evaluation order in if constexpr expression seems to be irrelevant for evaluating type traits

2018-06-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86282 --- Comment #4 from Jonathan Wakely --- (In reply to rene.rahn from comment #2) > thanks for enlighten me. Before, it wasn't clear to me, that if the nested > version works, the conjunction does not necessarily. The magic "does not get

[Bug c++/86282] Evaluation order in if constexpr expression seems to be irrelevant for evaluating type traits

2018-06-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86282 --- Comment #3 from Jonathan Wakely --- Using std::conjunction: template using has_begin2 = std::bool_constant>; template struct has_nested_begin { // ill-formed unless has_begin is true: static constexpr bool value =

[Bug c++/86282] Evaluation order in if constexpr expression seems to be irrelevant for evaluating type traits

2018-06-22 Thread rene.r...@fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86282 --- Comment #2 from rene.r...@fu-berlin.de --- Hi Jonathan, thanks for enlighten me. Before, it wasn't clear to me, that if the nested version works, the conjunction does not necessarily.

[Bug c++/86282] Evaluation order in if constexpr expression seems to be irrelevant for evaluating type traits

2018-06-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86282 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---