<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Character Set Management on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/character-set-management/</link><description>Recent content in Character Set Management on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 01 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/character-set-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 4: Refining Character Set Management</title><link>https://ai-blog.noorshomelab.dev/rust-password-generator-guide/chapter-04-implementing-character-sets/</link><pubDate>Mon, 01 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/rust-password-generator-guide/chapter-04-implementing-character-sets/</guid><description>&lt;h3 id="purpose-of-this-chapter"&gt;Purpose of This Chapter&lt;/h3&gt;
&lt;p&gt;While our current character set management works, it can become cumbersome as we add more options (e.g., excluding ambiguous characters). This chapter will refine our character set logic by introducing a more structured approach, making it easier to manage which characters are included or excluded. We&amp;rsquo;ll also ensure a sensible default where at least &lt;em&gt;some&lt;/em&gt; character types are always selected.&lt;/p&gt;
&lt;h3 id="concepts-explained"&gt;Concepts Explained&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Character Enums/Structs:&lt;/strong&gt; Instead of simply using boolean flags and &lt;code&gt;String::push_str&lt;/code&gt;, we can represent character sets more abstractly. This might involve creating an enum for character types or a helper struct that encapsulates the character pools and their selection logic. For this chapter, we&amp;rsquo;ll keep it fairly direct but improve the &lt;code&gt;main&lt;/code&gt; function&amp;rsquo;s structure.&lt;/p&gt;</description></item></channel></rss>