<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Template-Metaprogramming on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/template-metaprogramming/</link>
    <description>Recent content in Template-Metaprogramming on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/template-metaprogramming/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>C&#43;&#43; Template Metaprogramming Libraries: Boost.Hana vs Boost.Mp11 vs Brigand vs Metal</title>
      <link>https://www.pistack.xyz/posts/2026-06-22-cpp-template-metaprogramming-libraries-hana-mp11-brigand-metal/</link>
      <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-22-cpp-template-metaprogramming-libraries-hana-mp11-brigand-metal/</guid>
      <description>&lt;p&gt;C++ template metaprogramming has come a long way from the cryptic SFINAE tricks of C++98. Modern C++11/14/17/20 provides constexpr, fold expressions, concepts, and improved type traits that make compile-time computation both more powerful and more readable. However, working with the raw standard library type traits can still be verbose and error-prone. This is where template metaprogramming libraries step in — they provide higher-level abstractions that make compile-time computation feel almost like runtime programming.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
