<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cppcoro on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cppcoro/</link>
    <description>Recent content in Cppcoro 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/cppcoro/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted C&#43;&#43;20 Coroutine Libraries: cppcoro vs Boost.Cobalt vs concurrencpp</title>
      <link>https://www.pistack.xyz/posts/2026-06-22-cpp20-coroutine-libraries-cppcoro-boostcobalt-concurrencpp/</link>
      <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-22-cpp20-coroutine-libraries-cppcoro-boostcobalt-concurrencpp/</guid>
      <description>&lt;p&gt;Coroutines are the most transformative C++ feature since move semantics. With C++20, the language gained native coroutine support through the &lt;code&gt;co_await&lt;/code&gt;, &lt;code&gt;co_yield&lt;/code&gt;, and &lt;code&gt;co_return&lt;/code&gt; keywords — but the standard library did not provide any concrete coroutine types. This intentional gap left the ecosystem to innovate, and three libraries have emerged as the leading options: &lt;strong&gt;cppcoro&lt;/strong&gt; by Lewis Baker, &lt;strong&gt;Boost.Cobalt&lt;/strong&gt; from the Boost organization, and &lt;strong&gt;concurrencpp&lt;/strong&gt; by David Haim.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
