<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Result on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/result/</link><description>Recent content in Result on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Fri, 22 May 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/result/rss.xml" rel="self" type="application/rss+xml"/><item><title>Error Handling and Lifetimes: Result, Option, and Compile-Time Borrow Checking</title><link>https://blog.mickeyzzc.tech/en/posts/programming/rust-error-handling-lifetimes/</link><pubDate>Fri, 22 May 2026 10:00:00 +0800</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/programming/rust-error-handling-lifetimes/</guid><description>&lt;p&gt;If you&amp;rsquo;re used to Go&amp;rsquo;s &lt;code&gt;if err != nil&lt;/code&gt;, encountering Rust&amp;rsquo;s error handling for the first time can be confusing. Go&amp;rsquo;s philosophy is explicit multi-return values, where errors are just ordinary values. Rust, on the other hand, elevates error handling to the type system level—a function that might fail must declare it explicitly in its return type. This design brings zero-cost abstractions but also introduces the two concepts that give beginners the most headaches: the &lt;code&gt;Result&amp;lt;T, E&amp;gt;&lt;/code&gt; enum and lifetime annotations.&lt;/p&gt;</description></item></channel></rss>