<?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>Rust on Ultramaxu&#39;s blog</title>
    <link>https://blog.ultramaxu.me/tags/rust/</link>
    <description>Recent content in Rust on Ultramaxu&#39;s blog</description>
    <generator>Hugo -- 0.128.0</generator>
    <language>en</language>
    <lastBuildDate>Fri, 05 Jul 2024 05:53:24 +0200</lastBuildDate>
    <atom:link href="https://blog.ultramaxu.me/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taking screenshots with Xlib and Rust</title>
      <link>https://blog.ultramaxu.me/posts/taking_screenshots_with_xlib/</link>
      <pubDate>Fri, 05 Jul 2024 05:53:24 +0200</pubDate>
      <guid>https://blog.ultramaxu.me/posts/taking_screenshots_with_xlib/</guid>
      <description>But why? As I layed down the various requirements for my game engine, a requirement that seemed of vital importance was the ability to tests shaders and other graphical features. I live and breathe by TDD but I cannot do integration tests with a driver such as Vulkan or OpenGL (or maybe I can just not willing to do down this rabbit hole). An alternative is to do visual regression testing.</description>
    </item>
  </channel>
</rss>
