<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Copy on Home</title>
    <link>https://blog.rafaelfernandez.dev/tags/copy/</link>
    <description>Recent content in Copy on Home</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Rafael Fernandez</copyright>
    <lastBuildDate>Fri, 06 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.rafaelfernandez.dev/tags/copy/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Ownership in Rust 1. Stop fearing .clone()</title>
      <link>https://blog.rafaelfernandez.dev/posts/ownership-rust-1-stop-fearing-clone/</link>
      <pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.rafaelfernandez.dev/posts/ownership-rust-1-stop-fearing-clone/</guid>
      <description>The Rust community treats .clone() like a code smell. Sometimes it is. But most of the time, the instinct to avoid it costs more in complexity than the clone costs in nanoseconds. We dissect what clone actually does for every common type, the real cost spectrum across six orders of magnitude, and why Clone and Copy are not the same conversation.</description>
      
    </item>
    
  </channel>
</rss>
