<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Use on ErrorVault — Developer Error Code Dictionary</title>
    <link>https://errorvault.dev/tags/use/</link>
    <description>Recent content in Use on ErrorVault — Developer Error Code Dictionary</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 21 Jul 2026 10:20:04 +0800</lastBuildDate>
    <atom:link href="https://errorvault.dev/tags/use/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fix E0428: Conflicting Import Names in Rust</title>
      <link>https://errorvault.dev/rust/rust-e0428-conflicting-import-names/</link>
      <pubDate>Tue, 21 Jul 2026 10:20:04 +0800</pubDate>
      <guid>https://errorvault.dev/rust/rust-e0428-conflicting-import-names/</guid>
      <description>&lt;h1 id=&#34;fix-e0428-conflicting-import-names-in-rust&#34;&gt;Fix E0428: Conflicting Import Names in Rust&lt;/h1&gt;&#xA;&lt;p&gt;Rust&amp;rsquo;s strict module system and type safety ensure that ambiguous names are flagged at compile time rather than causing runtime confusion. Error code E0428 signals that the compiler has encountered a name collision where the same identifier exists in multiple scopes and cannot be unambiguously resolved. This error typically arises during module imports when two or more &lt;code&gt;use&lt;/code&gt; statements bring identically named items into the same namespace, or when an imported name clashes with a locally defined item. Understanding the mechanics of Rust&amp;rsquo;s import resolution is essential for writing clean, maintainable code that compiles without ambiguity.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
