<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Collections on m58 | DevSecOps &amp; Pentest</title><link>https://0xm58.xyz/tags/collections/</link><description>Recent content in Collections on m58 | DevSecOps &amp; Pentest</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://0xm58.xyz/tags/collections/index.xml" rel="self" type="application/rss+xml"/><item><title>Rust basics: strings, vectors, and slices</title><link>https://0xm58.xyz/posts/rust-strings-vectors-and-slices/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://0xm58.xyz/posts/rust-strings-vectors-and-slices/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 Many beginner Rust questions are really collection questions in disguise. Most of them come down to four types: &lt;code&gt;String&lt;/code&gt;, &lt;code&gt;&amp;amp;str&lt;/code&gt;, &lt;code&gt;Vec&amp;lt;T&amp;gt;&lt;/code&gt;, and slices like &lt;code&gt;&amp;amp;[T]&lt;/code&gt;.
&lt;/div&gt;

&lt;p&gt;These types are connected. If you learn them together, Rust&amp;rsquo;s API style becomes much easier to read.&lt;/p&gt;</description></item></channel></rss>