<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>code structure on Digitable Courses</title>
    <link>https://courses.digitable.life/en/tags/code-structure/</link>
    <description>Recent content in code structure on Digitable Courses</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 03 Sep 2026 10:00:00 +0300</lastBuildDate><atom:link href="https://courses.digitable.life/en/tags/code-structure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Inside digitdisk: 2,206 lines of flang decide, 20,678 lines of Go act</title>
      <link>https://courses.digitable.life/en/post/digitdisk-inside/</link>
      <pubDate>Thu, 03 Sep 2026 10:00:00 +0300</pubDate>
      
      <guid>https://courses.digitable.life/en/post/digitdisk-inside/</guid>
      <description>A walk through the digitdisk source tree: the decisions live in a flang core with 14 postconditions, the conversation with the operating system lives in a Go host with not one external dependency. The screen does not go around the deciding layer: Backspace erases for good, yet the plan is built by the same function an ordinary cleanup uses. The screen layout exists in two implementations, and a run demands that both produce the same frame byte for byte. On a Mac nine Mach symbols are called without cgo. Every number here names the command that prints it.</description>
    </item>
    
  </channel>
</rss>
