<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Polymorphism on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/polymorphism/</link>
    <description>Recent content in Polymorphism on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/polymorphism/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted C&#43;&#43; Type Erasure Libraries: Proxy vs Dyno vs Boost.TypeErasure vs function2</title>
      <link>https://www.pistack.xyz/posts/2026-06-29-cpp-type-erasure-libraries-proxy-dyno-boost-function2/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-29-cpp-type-erasure-libraries-proxy-dyno-boost-function2/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Classical object-oriented polymorphism in C++ relies on inheritance and virtual functions. While powerful, this approach forces all participating types into a common base class hierarchy, requires heap allocation, and introduces vtable indirection. &lt;strong&gt;Type erasure&lt;/strong&gt; is an alternative technique that provides runtime polymorphism without inheritance — any type that satisfies a set of requirements (duck typing) can be used interchangeably, without modifying the type itself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
