<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rjeli</author><text>The amount of background knowledge you need to understand what’s happening here... I don’t envy people who have to catch up&lt;p&gt;becoming more and more convinced that when sfinae opened the Turing hatch it doomed c++</text><parent_chain></parent_chain></comment><story><title>A quick primer on type traits in modern C++</title><url>https://www.internalpointers.com/post/quick-primer-type-traits-modern-cpp</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>RossBencina</author><text>I found the use of &amp;#x27;if constexpr&amp;#x27; in the example pretty nasty. I would have thought it more idiomatic to use std::enable_if to enable different implementations of &amp;#x27;algorithm&amp;#x27; as in the example of &amp;#x27;construct&amp;#x27; and &amp;#x27;destroy&amp;#x27; given here:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.cppreference.com&amp;#x2F;w&amp;#x2F;cpp&amp;#x2F;types&amp;#x2F;enable_if&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.cppreference.com&amp;#x2F;w&amp;#x2F;cpp&amp;#x2F;types&amp;#x2F;enable_if&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>A quick primer on type traits in modern C++</title><url>https://www.internalpointers.com/post/quick-primer-type-traits-modern-cpp</url></story>