<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Recursive-Schema on martinuke0&#39;s Blog</title>
    <link>https://martinuke0.github.io/tags/recursive-schema/</link>
    <description>Recent content in Recursive-Schema on martinuke0&#39;s Blog</description>
    <image>
      <title>martinuke0&#39;s Blog</title>
      <url>https://martinuke0.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://martinuke0.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <lastBuildDate>Fri, 15 May 2026 11:53:28 +0000</lastBuildDate>
    <atom:link href="https://martinuke0.github.io/tags/recursive-schema/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Zero-Copy Deserialization Fails for Large Recursive Schemas</title>
      <link>https://martinuke0.github.io/posts/2026-05-15-why-zero-copy-deserialization-fails-for-large-recursive-schemas/</link>
      <pubDate>Fri, 15 May 2026 11:53:28 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-05-15-why-zero-copy-deserialization-fails-for-large-recursive-schemas/</guid>
      <description>Zero-copy deserialization sounds ideal, but with deep recursive data structures it can cause stack overflows, lifetime violations, and memory bloat, making it impractical for large schemas.</description>
    </item>
  </channel>
</rss>
