<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Statics on rustbites</title><link>https://www.rustbites.com/tags/statics/</link><description>Recent content in Statics on rustbites</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 06 May 2026 14:47:50 +0200</lastBuildDate><atom:link href="https://www.rustbites.com/tags/statics/index.xml" rel="self" type="application/rss+xml"/><item><title>120. OnceLock — Lazy Statics That Initialize on Your Schedule</title><link>https://www.rustbites.com/posts/bite-120/</link><pubDate>Tue, 05 May 2026 09:00:00 +0100</pubDate><guid>https://www.rustbites.com/posts/bite-120/</guid><description>&lt;p&gt;&lt;code&gt;LazyLock&lt;/code&gt; runs its initializer the first time anyone touches the value — fine when the inputs are baked in at compile time, useless when you only learn them at runtime. &lt;code&gt;OnceLock&lt;/code&gt; is the same idea, but you decide when (and with what data) initialization happens.&lt;/p&gt;</description></item></channel></rss>