<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Error-Handling on m58 | DevSecOps &amp; Pentest</title><link>https://0xm58.xyz/tags/error-handling/</link><description>Recent content in Error-Handling on m58 | DevSecOps &amp; Pentest</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://0xm58.xyz/tags/error-handling/index.xml" rel="self" type="application/rss+xml"/><item><title>Rust basics: Option and Result</title><link>https://0xm58.xyz/posts/rust-option-and-result/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://0xm58.xyz/posts/rust-option-and-result/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 Rust does not use &lt;code&gt;null&lt;/code&gt; for ordinary absence, and it does not rely on exceptions for recoverable errors. Instead, it uses enums: &lt;code&gt;Option&amp;lt;T&amp;gt;&lt;/code&gt; and &lt;code&gt;Result&amp;lt;T, E&amp;gt;&lt;/code&gt;.
&lt;/div&gt;

&lt;p&gt;These two types show up everywhere. If you understand them early, a lot of Rust APIs stop looking strange.&lt;/p&gt;</description></item></channel></rss>