<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lazy-Initialization on rustbites</title><link>https://www.rustbites.com/tags/lazy-initialization/</link><description>Recent content in Lazy-Initialization on rustbites</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 08 Jun 2026 11:56:48 +0200</lastBuildDate><atom:link href="https://www.rustbites.com/tags/lazy-initialization/index.xml" rel="self" type="application/rss+xml"/><item><title>188. LazyLock::from — Skip the Closure When You Already Have the Value</title><link>https://www.rustbites.com/posts/bite-188/</link><pubDate>Sun, 07 Jun 2026 17:00:00 +0100</pubDate><guid>https://www.rustbites.com/posts/bite-188/</guid><description>&lt;p&gt;Sometimes your &amp;ldquo;lazy&amp;rdquo; value isn&amp;rsquo;t lazy at all — a test or a CLI flag hands it to you up front. Rust 1.96 stabilized &lt;code&gt;From&amp;lt;T&amp;gt; for LazyLock&amp;lt;T&amp;gt;&lt;/code&gt;, so you can build an already-initialized lock straight from the value.&lt;/p&gt;</description></item></channel></rss>