<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Bloggings</title><link>https://mfroeh.github.io/posts/</link><description>Recent content in Posts on Bloggings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mfroeh.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>On Strings in Rust</title><link>https://mfroeh.github.io/2026/07/on-strings-in-rust/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://mfroeh.github.io/2026/07/on-strings-in-rust/</guid><description>&lt;p&gt;Strings in Rust are &lt;strong&gt;not&lt;/strong&gt; simple, and perhaps not the easiest starting point when learning Rust. There is more to Rust strings than initially meets the eye, and when learning to understand them, you encounter a large variety of Rust-specific concepts that pervade the language as a whole. The concepts touched in this post are: slices (and thus dynamically sized types, &lt;code&gt;?Sized&lt;/code&gt;, wide/fat pointers), iterators, deref coercion, dot operator semantics, operator overloading, and Unicode (not specific to Rust, but still useful to know).&lt;/p&gt;</description></item></channel></rss>