<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rust on Ian Luckraft - Software Engineer</title>
    <link>https://ianluckraft.co.uk/categories/rust/</link>
    <description>Recent content in Rust on Ian Luckraft - Software Engineer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 09 Nov 2026 11:00:00 +0000</lastBuildDate><atom:link href="https://ianluckraft.co.uk/categories/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rust Errors Explained</title>
      <link>https://ianluckraft.co.uk/2026/1/rust-errors-explained/</link>
      <pubDate>Mon, 09 Nov 2026 11:00:00 +0000</pubDate>
      
      <guid>https://ianluckraft.co.uk/2026/1/rust-errors-explained/</guid>
      <description>Rust Errors Explained: Learning to Read the Compiler Instead of Fearing It #  If you’ve spent any time with Rust as a beginner you already know the feeling. You write what looks like a reasonable few lines of code, hit compile, and the terminal lights up with red underlines, error codes, and hints that somehow make less sense the longer you stare at them.
It’s easy to walk away thinking the language is hostile.</description>
    </item>
    
  </channel>
</rss>
