build: 2026-06-22
This commit is contained in:
699
build/ch15-06-reference-cycles.html
Normal file
699
build/ch15-06-reference-cycles.html
Normal file
@@ -0,0 +1,699 @@
|
||||
<!DOCTYPE HTML>
|
||||
<html lang="en" class="light sidebar-visible" dir="ltr">
|
||||
<head>
|
||||
<!-- Book generated using mdBook -->
|
||||
<meta charset="UTF-8">
|
||||
<title>Reference Cycles Can Leak Memory - The Rust Programming Language</title>
|
||||
|
||||
|
||||
<!-- Custom HTML head -->
|
||||
|
||||
<meta name="description" content="">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="theme-color" content="#ffffff">
|
||||
|
||||
<link rel="icon" href="favicon-de23e50b.svg">
|
||||
<link rel="shortcut icon" href="favicon-8114d1fc.png">
|
||||
<link rel="stylesheet" href="css/variables-8adf115d.css">
|
||||
<link rel="stylesheet" href="css/general-0392ca55.css">
|
||||
<link rel="stylesheet" href="css/chrome-fc474251.css">
|
||||
<link rel="stylesheet" href="css/print-9e4910d8.css" media="print">
|
||||
|
||||
<!-- Fonts -->
|
||||
<link rel="stylesheet" href="fonts/fonts-9644e21d.css">
|
||||
|
||||
<!-- Highlight.js Stylesheets -->
|
||||
<link rel="stylesheet" id="mdbook-highlight-css" href="highlight-493f70e1.css">
|
||||
<link rel="stylesheet" id="mdbook-tomorrow-night-css" href="tomorrow-night-4c0ae647.css">
|
||||
<link rel="stylesheet" id="mdbook-ayu-highlight-css" href="ayu-highlight-3fdfc3ac.css">
|
||||
|
||||
<!-- Custom theme stylesheets -->
|
||||
<link rel="stylesheet" href="ferris-d33b75bf.css">
|
||||
<link rel="stylesheet" href="theme/2018-edition-4e126c62.css">
|
||||
<link rel="stylesheet" href="theme/semantic-notes-9b5766c0.css">
|
||||
<link rel="stylesheet" href="theme/listing-cab26221.css">
|
||||
|
||||
|
||||
<!-- Provide site root and default themes to javascript -->
|
||||
<script>
|
||||
const path_to_root = "";
|
||||
const default_light_theme = "light";
|
||||
const default_dark_theme = "navy";
|
||||
window.path_to_searchindex_js = "searchindex-6a1da8cc.js";
|
||||
</script>
|
||||
<!-- Start loading toc.js asap -->
|
||||
<script src="toc-0e4ce700.js"></script>
|
||||
</head>
|
||||
<body>
|
||||
<div id="mdbook-help-container">
|
||||
<div id="mdbook-help-popup">
|
||||
<h2 class="mdbook-help-title">Keyboard shortcuts</h2>
|
||||
<div>
|
||||
<p>Press <kbd>←</kbd> or <kbd>→</kbd> to navigate between chapters</p>
|
||||
<p>Press <kbd>S</kbd> or <kbd>/</kbd> to search in the book</p>
|
||||
<p>Press <kbd>?</kbd> to show this help</p>
|
||||
<p>Press <kbd>Esc</kbd> to hide this help</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div id="mdbook-body-container">
|
||||
<!-- Work around some values being stored in localStorage wrapped in quotes -->
|
||||
<script>
|
||||
try {
|
||||
let theme = localStorage.getItem('mdbook-theme');
|
||||
let sidebar = localStorage.getItem('mdbook-sidebar');
|
||||
|
||||
if (theme.startsWith('"') && theme.endsWith('"')) {
|
||||
localStorage.setItem('mdbook-theme', theme.slice(1, theme.length - 1));
|
||||
}
|
||||
|
||||
if (sidebar.startsWith('"') && sidebar.endsWith('"')) {
|
||||
localStorage.setItem('mdbook-sidebar', sidebar.slice(1, sidebar.length - 1));
|
||||
}
|
||||
} catch (e) { }
|
||||
</script>
|
||||
|
||||
<!-- Set the theme before any content is loaded, prevents flash -->
|
||||
<script>
|
||||
const default_theme = window.matchMedia("(prefers-color-scheme: dark)").matches ? default_dark_theme : default_light_theme;
|
||||
let theme;
|
||||
try { theme = localStorage.getItem('mdbook-theme'); } catch(e) { }
|
||||
if (theme === null || theme === undefined) { theme = default_theme; }
|
||||
const html = document.documentElement;
|
||||
html.classList.remove('light')
|
||||
html.classList.add(theme);
|
||||
html.classList.add("js");
|
||||
</script>
|
||||
|
||||
<input type="checkbox" id="mdbook-sidebar-toggle-anchor" class="hidden">
|
||||
|
||||
<!-- Hide / unhide sidebar before it is displayed -->
|
||||
<script>
|
||||
let sidebar = null;
|
||||
const sidebar_toggle = document.getElementById("mdbook-sidebar-toggle-anchor");
|
||||
if (document.body.clientWidth >= 1080) {
|
||||
try { sidebar = localStorage.getItem('mdbook-sidebar'); } catch(e) { }
|
||||
sidebar = sidebar || 'visible';
|
||||
} else {
|
||||
sidebar = 'hidden';
|
||||
sidebar_toggle.checked = false;
|
||||
}
|
||||
if (sidebar === 'visible') {
|
||||
sidebar_toggle.checked = true;
|
||||
} else {
|
||||
html.classList.remove('sidebar-visible');
|
||||
}
|
||||
</script>
|
||||
|
||||
<nav id="mdbook-sidebar" class="sidebar" aria-label="Table of contents">
|
||||
<!-- populated by js -->
|
||||
<mdbook-sidebar-scrollbox class="sidebar-scrollbox"></mdbook-sidebar-scrollbox>
|
||||
<noscript>
|
||||
<iframe class="sidebar-iframe-outer" src="toc.html"></iframe>
|
||||
</noscript>
|
||||
<div id="mdbook-sidebar-resize-handle" class="sidebar-resize-handle">
|
||||
<div class="sidebar-resize-indicator"></div>
|
||||
</div>
|
||||
</nav>
|
||||
|
||||
<div id="mdbook-page-wrapper" class="page-wrapper">
|
||||
|
||||
<div class="page">
|
||||
<div id="mdbook-menu-bar-hover-placeholder"></div>
|
||||
<div id="mdbook-menu-bar" class="menu-bar sticky">
|
||||
<div class="left-buttons">
|
||||
<label id="mdbook-sidebar-toggle" class="icon-button" for="mdbook-sidebar-toggle-anchor" title="Toggle Table of Contents" aria-label="Toggle Table of Contents" aria-controls="mdbook-sidebar">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M0 96C0 78.3 14.3 64 32 64H416c17.7 0 32 14.3 32 32s-14.3 32-32 32H32C14.3 128 0 113.7 0 96zM0 256c0-17.7 14.3-32 32-32H416c17.7 0 32 14.3 32 32s-14.3 32-32 32H32c-17.7 0-32-14.3-32-32zM448 416c0 17.7-14.3 32-32 32H32c-17.7 0-32-14.3-32-32s14.3-32 32-32H416c17.7 0 32 14.3 32 32z"/></svg></span>
|
||||
</label>
|
||||
<button id="mdbook-theme-toggle" class="icon-button" type="button" title="Change theme" aria-label="Change theme" aria-haspopup="true" aria-expanded="false" aria-controls="mdbook-theme-list">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M371.3 367.1c27.3-3.9 51.9-19.4 67.2-42.9L600.2 74.1c12.6-19.5 9.4-45.3-7.6-61.2S549.7-4.4 531.1 9.6L294.4 187.2c-24 18-38.2 46.1-38.4 76.1L371.3 367.1zm-19.6 25.4l-116-104.4C175.9 290.3 128 339.6 128 400c0 3.9 .2 7.8 .6 11.6c1.8 17.5-10.2 36.4-27.8 36.4H96c-17.7 0-32 14.3-32 32s14.3 32 32 32H240c61.9 0 112-50.1 112-112c0-2.5-.1-5-.2-7.5z"/></svg></span>
|
||||
</button>
|
||||
<ul id="mdbook-theme-list" class="theme-popup" aria-label="Themes" role="menu">
|
||||
<li role="none"><button role="menuitem" class="theme" id="mdbook-theme-default_theme">Auto</button></li>
|
||||
<li role="none"><button role="menuitem" class="theme" id="mdbook-theme-light">Light</button></li>
|
||||
<li role="none"><button role="menuitem" class="theme" id="mdbook-theme-rust">Rust</button></li>
|
||||
<li role="none"><button role="menuitem" class="theme" id="mdbook-theme-coal">Coal</button></li>
|
||||
<li role="none"><button role="menuitem" class="theme" id="mdbook-theme-navy">Navy</button></li>
|
||||
<li role="none"><button role="menuitem" class="theme" id="mdbook-theme-ayu">Ayu</button></li>
|
||||
</ul>
|
||||
<button id="mdbook-search-toggle" class="icon-button" type="button" title="Search (`/`)" aria-label="Toggle Searchbar" aria-expanded="false" aria-keyshortcuts="/ s" aria-controls="mdbook-searchbar">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M416 208c0 45.9-14.9 88.3-40 122.7L502.6 457.4c12.5 12.5 12.5 32.8 0 45.3s-32.8 12.5-45.3 0L330.7 376c-34.4 25.2-76.8 40-122.7 40C93.1 416 0 322.9 0 208S93.1 0 208 0S416 93.1 416 208zM208 352c79.5 0 144-64.5 144-144s-64.5-144-144-144S64 128.5 64 208s64.5 144 144 144z"/></svg></span>
|
||||
</button>
|
||||
</div>
|
||||
|
||||
<h1 class="menu-title">The Rust Programming Language</h1>
|
||||
|
||||
<div class="right-buttons">
|
||||
<a href="print.html" title="Print this book" aria-label="Print this book">
|
||||
<span class=fa-svg id="print-button"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M128 0C92.7 0 64 28.7 64 64v96h64V64H354.7L384 93.3V160h64V93.3c0-17-6.7-33.3-18.7-45.3L400 18.7C388 6.7 371.7 0 354.7 0H128zM384 352v32 64H128V384 368 352H384zm64 32h32c17.7 0 32-14.3 32-32V256c0-35.3-28.7-64-64-64H64c-35.3 0-64 28.7-64 64v96c0 17.7 14.3 32 32 32H64v64c0 35.3 28.7 64 64 64H384c35.3 0 64-28.7 64-64V384zm-16-88c-13.3 0-24-10.7-24-24s10.7-24 24-24s24 10.7 24 24s-10.7 24-24 24z"/></svg></span>
|
||||
</a>
|
||||
<a href="https://github.com/rust-lang/book" title="Git repository" aria-label="Git repository">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 496 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6zm-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3zm44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9zM244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8zM97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1zm-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7zm32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1zm-11.4-14.7c-1.6 1-1.6 3.6 0 5.9 1.6 2.3 4.3 3.3 5.6 2.3 1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2z"/></svg></span>
|
||||
</a>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="mdbook-search-wrapper" class="hidden">
|
||||
<form id="mdbook-searchbar-outer" class="searchbar-outer">
|
||||
<div class="search-wrapper">
|
||||
<input type="search" id="mdbook-searchbar" name="searchbar" placeholder="Search this book ..." aria-controls="mdbook-searchresults-outer" aria-describedby="searchresults-header">
|
||||
<div class="spinner-wrapper">
|
||||
<span class=fa-svg id="fa-spin"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M304 48c0-26.5-21.5-48-48-48s-48 21.5-48 48s21.5 48 48 48s48-21.5 48-48zm0 416c0-26.5-21.5-48-48-48s-48 21.5-48 48s21.5 48 48 48s48-21.5 48-48zM48 304c26.5 0 48-21.5 48-48s-21.5-48-48-48s-48 21.5-48 48s21.5 48 48 48zm464-48c0-26.5-21.5-48-48-48s-48 21.5-48 48s21.5 48 48 48s48-21.5 48-48zM142.9 437c18.7-18.7 18.7-49.1 0-67.9s-49.1-18.7-67.9 0s-18.7 49.1 0 67.9s49.1 18.7 67.9 0zm0-294.2c18.7-18.7 18.7-49.1 0-67.9S93.7 56.2 75 75s-18.7 49.1 0 67.9s49.1 18.7 67.9 0zM369.1 437c18.7 18.7 49.1 18.7 67.9 0s18.7-49.1 0-67.9s-49.1-18.7-67.9 0s-18.7 49.1 0 67.9z"/></svg></span>
|
||||
</div>
|
||||
</div>
|
||||
</form>
|
||||
<div id="mdbook-searchresults-outer" class="searchresults-outer hidden">
|
||||
<div id="mdbook-searchresults-header" class="searchresults-header"></div>
|
||||
<ul id="mdbook-searchresults">
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<!-- Apply ARIA attributes after the sidebar and the sidebar toggle button are added to the DOM -->
|
||||
<script>
|
||||
document.getElementById('mdbook-sidebar-toggle').setAttribute('aria-expanded', sidebar === 'visible');
|
||||
document.getElementById('mdbook-sidebar').setAttribute('aria-hidden', sidebar !== 'visible');
|
||||
Array.from(document.querySelectorAll('#mdbook-sidebar a')).forEach(function(link) {
|
||||
link.setAttribute('tabIndex', sidebar === 'visible' ? 0 : -1);
|
||||
});
|
||||
</script>
|
||||
|
||||
<div id="mdbook-content" class="content">
|
||||
<main>
|
||||
<h2 id="reference-cycles-can-leak-memory"><a class="header" href="#reference-cycles-can-leak-memory">Reference Cycles Can Leak Memory</a></h2>
|
||||
<p>Rust’s memory safety guarantees make it difficult, but not impossible, to
|
||||
accidentally create memory that is never cleaned up (known as a <em>memory leak</em>).
|
||||
Preventing memory leaks entirely is not one of Rust’s guarantees, meaning
|
||||
memory leaks are memory safe in Rust. We can see that Rust allows memory leaks
|
||||
by using <code>Rc<T></code> and <code>RefCell<T></code>: It’s possible to create references where
|
||||
items refer to each other in a cycle. This creates memory leaks because the
|
||||
reference count of each item in the cycle will never reach 0, and the values
|
||||
will never be dropped.</p>
|
||||
<h3 id="creating-a-reference-cycle"><a class="header" href="#creating-a-reference-cycle">Creating a Reference Cycle</a></h3>
|
||||
<p>Let’s look at how a reference cycle might happen and how to prevent it,
|
||||
starting with the definition of the <code>List</code> enum and a <code>tail</code> method in Listing
|
||||
15-25.</p>
|
||||
<figure class="listing" id="listing-15-25">
|
||||
<span class="file-name">Filename: src/main.rs</span>
|
||||
<pre class="playground"><code class="language-rust edition2024">use crate::List::{Cons, Nil};
|
||||
use std::cell::RefCell;
|
||||
use std::rc::Rc;
|
||||
|
||||
#[derive(Debug)]
|
||||
enum List {
|
||||
Cons(i32, RefCell<Rc<List>>),
|
||||
Nil,
|
||||
}
|
||||
|
||||
impl List {
|
||||
fn tail(&self) -> Option<&RefCell<Rc<List>>> {
|
||||
match self {
|
||||
Cons(_, item) => Some(item),
|
||||
Nil => None,
|
||||
}
|
||||
}
|
||||
}
|
||||
<span class="boring">
|
||||
</span><span class="boring">fn main() {}</span></code></pre>
|
||||
<figcaption><a href="#listing-15-25">Listing 15-25</a>: A cons list definition that holds a <code>RefCell<T></code> so that we can modify what a <code>Cons</code> variant is referring to</figcaption>
|
||||
</figure>
|
||||
<p>We’re using another variation of the <code>List</code> definition from Listing 15-5. The
|
||||
second element in the <code>Cons</code> variant is now <code>RefCell<Rc<List>></code>, meaning that
|
||||
instead of having the ability to modify the <code>i32</code> value as we did in Listing
|
||||
15-24, we want to modify the <code>List</code> value a <code>Cons</code> variant is pointing to.
|
||||
We’re also adding a <code>tail</code> method to make it convenient for us to access the
|
||||
second item if we have a <code>Cons</code> variant.</p>
|
||||
<p>In Listing 15-26, we’re adding a <code>main</code> function that uses the definitions in
|
||||
Listing 15-25. This code creates a list in <code>a</code> and a list in <code>b</code> that points to
|
||||
the list in <code>a</code>. Then, it modifies the list in <code>a</code> to point to <code>b</code>, creating a
|
||||
reference cycle. There are <code>println!</code> statements along the way to show what the
|
||||
reference counts are at various points in this process.</p>
|
||||
<figure class="listing" id="listing-15-26">
|
||||
<span class="file-name">Filename: src/main.rs</span>
|
||||
<pre class="playground"><code class="language-rust edition2024"><span class="boring">use crate::List::{Cons, Nil};
|
||||
</span><span class="boring">use std::cell::RefCell;
|
||||
</span><span class="boring">use std::rc::Rc;
|
||||
</span><span class="boring">
|
||||
</span><span class="boring">#[derive(Debug)]
|
||||
</span><span class="boring">enum List {
|
||||
</span><span class="boring"> Cons(i32, RefCell<Rc<List>>),
|
||||
</span><span class="boring"> Nil,
|
||||
</span><span class="boring">}
|
||||
</span><span class="boring">
|
||||
</span><span class="boring">impl List {
|
||||
</span><span class="boring"> fn tail(&self) -> Option<&RefCell<Rc<List>>> {
|
||||
</span><span class="boring"> match self {
|
||||
</span><span class="boring"> Cons(_, item) => Some(item),
|
||||
</span><span class="boring"> Nil => None,
|
||||
</span><span class="boring"> }
|
||||
</span><span class="boring"> }
|
||||
</span><span class="boring">}
|
||||
</span><span class="boring">
|
||||
</span>fn main() {
|
||||
let a = Rc::new(Cons(5, RefCell::new(Rc::new(Nil))));
|
||||
|
||||
println!("a initial rc count = {}", Rc::strong_count(&a));
|
||||
println!("a next item = {:?}", a.tail());
|
||||
|
||||
let b = Rc::new(Cons(10, RefCell::new(Rc::clone(&a))));
|
||||
|
||||
println!("a rc count after b creation = {}", Rc::strong_count(&a));
|
||||
println!("b initial rc count = {}", Rc::strong_count(&b));
|
||||
println!("b next item = {:?}", b.tail());
|
||||
|
||||
if let Some(link) = a.tail() {
|
||||
*link.borrow_mut() = Rc::clone(&b);
|
||||
}
|
||||
|
||||
println!("b rc count after changing a = {}", Rc::strong_count(&b));
|
||||
println!("a rc count after changing a = {}", Rc::strong_count(&a));
|
||||
|
||||
// Uncomment the next line to see that we have a cycle;
|
||||
// it will overflow the stack.
|
||||
// println!("a next item = {:?}", a.tail());
|
||||
}</code></pre>
|
||||
<figcaption><a href="#listing-15-26">Listing 15-26</a>: Creating a reference cycle of two <code>List</code> values pointing to each other</figcaption>
|
||||
</figure>
|
||||
<p>We create an <code>Rc<List></code> instance holding a <code>List</code> value in the variable <code>a</code>
|
||||
with an initial list of <code>5, Nil</code>. We then create an <code>Rc<List></code> instance holding
|
||||
another <code>List</code> value in the variable <code>b</code> that contains the value <code>10</code> and
|
||||
points to the list in <code>a</code>.</p>
|
||||
<p>We modify <code>a</code> so that it points to <code>b</code> instead of <code>Nil</code>, creating a cycle. We
|
||||
do that by using the <code>tail</code> method to get a reference to the
|
||||
<code>RefCell<Rc<List>></code> in <code>a</code>, which we put in the variable <code>link</code>. Then, we use
|
||||
the <code>borrow_mut</code> method on the <code>RefCell<Rc<List>></code> to change the value inside
|
||||
from an <code>Rc<List></code> that holds a <code>Nil</code> value to the <code>Rc<List></code> in <code>b</code>.</p>
|
||||
<p>When we run this code, keeping the last <code>println!</code> commented out for the
|
||||
moment, we’ll get this output:</p>
|
||||
<pre><code class="language-console">$ cargo run
|
||||
Compiling cons-list v0.1.0 (file:///projects/cons-list)
|
||||
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.53s
|
||||
Running `target/debug/cons-list`
|
||||
a initial rc count = 1
|
||||
a next item = Some(RefCell { value: Nil })
|
||||
a rc count after b creation = 2
|
||||
b initial rc count = 1
|
||||
b next item = Some(RefCell { value: Cons(5, RefCell { value: Nil }) })
|
||||
b rc count after changing a = 2
|
||||
a rc count after changing a = 2
|
||||
</code></pre>
|
||||
<p>The reference count of the <code>Rc<List></code> instances in both <code>a</code> and <code>b</code> is 2 after
|
||||
we change the list in <code>a</code> to point to <code>b</code>. At the end of <code>main</code>, Rust drops the
|
||||
variable <code>b</code>, which decreases the reference count of the <code>b</code> <code>Rc<List></code>
|
||||
instance from 2 to 1. The memory that <code>Rc<List></code> has on the heap won’t be
|
||||
dropped at this point because its reference count is 1, not 0. Then, Rust drops
|
||||
<code>a</code>, which decreases the reference count of the <code>a</code> <code>Rc<List></code> instance from 2
|
||||
to 1 as well. This instance’s memory can’t be dropped either, because the other
|
||||
<code>Rc<List></code> instance still refers to it. The memory allocated to the list will
|
||||
remain uncollected forever. To visualize this reference cycle, we’ve created
|
||||
the diagram in Figure 15-4.</p>
|
||||
<img alt="A rectangle labeled 'a' that points to a rectangle containing the integer 5. A rectangle labeled 'b' that points to a rectangle containing the integer 10. The rectangle containing 5 points to the rectangle containing 10, and the rectangle containing 10 points back to the rectangle containing 5, creating a cycle." src="img/trpl15-04.svg" class="center" />
|
||||
<p><span class="caption">Figure 15-4: A reference cycle of lists <code>a</code> and <code>b</code>
|
||||
pointing to each other</span></p>
|
||||
<p>If you uncomment the last <code>println!</code> and run the program, Rust will try to
|
||||
print this cycle with <code>a</code> pointing to <code>b</code> pointing to <code>a</code> and so forth until it
|
||||
overflows the stack.</p>
|
||||
<p>Compared to a real-world program, the consequences of creating a reference
|
||||
cycle in this example aren’t very dire: Right after we create the reference
|
||||
cycle, the program ends. However, if a more complex program allocated lots of
|
||||
memory in a cycle and held onto it for a long time, the program would use more
|
||||
memory than it needed and might overwhelm the system, causing it to run out of
|
||||
available memory.</p>
|
||||
<p>Creating reference cycles is not easily done, but it’s not impossible either.
|
||||
If you have <code>RefCell<T></code> values that contain <code>Rc<T></code> values or similar nested
|
||||
combinations of types with interior mutability and reference counting, you must
|
||||
ensure that you don’t create cycles; you can’t rely on Rust to catch them.
|
||||
Creating a reference cycle would be a logic bug in your program that you should
|
||||
use automated tests, code reviews, and other software development practices to
|
||||
minimize.</p>
|
||||
<p>Another solution for avoiding reference cycles is reorganizing your data
|
||||
structures so that some references express ownership and some references don’t.
|
||||
As a result, you can have cycles made up of some ownership relationships and
|
||||
some non-ownership relationships, and only the ownership relationships affect
|
||||
whether or not a value can be dropped. In Listing 15-25, we always want <code>Cons</code>
|
||||
variants to own their list, so reorganizing the data structure isn’t possible.
|
||||
Let’s look at an example using graphs made up of parent nodes and child nodes
|
||||
to see when non-ownership relationships are an appropriate way to prevent
|
||||
reference cycles.</p>
|
||||
<!-- Old headings. Do not remove or links may break. -->
|
||||
<p><a id="preventing-reference-cycles-turning-an-rct-into-a-weakt"></a></p>
|
||||
<h3 id="preventing-reference-cycles-using-weakt"><a class="header" href="#preventing-reference-cycles-using-weakt">Preventing Reference Cycles Using <code>Weak<T></code></a></h3>
|
||||
<p>So far, we’ve demonstrated that calling <code>Rc::clone</code> increases the
|
||||
<code>strong_count</code> of an <code>Rc<T></code> instance, and an <code>Rc<T></code> instance is only cleaned
|
||||
up if its <code>strong_count</code> is 0. You can also create a weak reference to the
|
||||
value within an <code>Rc<T></code> instance by calling <code>Rc::downgrade</code> and passing a
|
||||
reference to the <code>Rc<T></code>. <em>Strong references</em> are how you can share ownership
|
||||
of an <code>Rc<T></code> instance. <em>Weak references</em> don’t express an ownership
|
||||
relationship, and their count doesn’t affect when an <code>Rc<T></code> instance is
|
||||
cleaned up. They won’t cause a reference cycle, because any cycle involving
|
||||
some weak references will be broken once the strong reference count of values
|
||||
involved is 0.</p>
|
||||
<p>When you call <code>Rc::downgrade</code>, you get a smart pointer of type <code>Weak<T></code>.
|
||||
Instead of increasing the <code>strong_count</code> in the <code>Rc<T></code> instance by 1, calling
|
||||
<code>Rc::downgrade</code> increases the <code>weak_count</code> by 1. The <code>Rc<T></code> type uses
|
||||
<code>weak_count</code> to keep track of how many <code>Weak<T></code> references exist, similar to
|
||||
<code>strong_count</code>. The difference is the <code>weak_count</code> doesn’t need to be 0 for the
|
||||
<code>Rc<T></code> instance to be cleaned up.</p>
|
||||
<p>Because the value that <code>Weak<T></code> references might have been dropped, to do
|
||||
anything with the value that a <code>Weak<T></code> is pointing to you must make sure the
|
||||
value still exists. Do this by calling the <code>upgrade</code> method on a <code>Weak<T></code>
|
||||
instance, which will return an <code>Option<Rc<T>></code>. You’ll get a result of <code>Some</code>
|
||||
if the <code>Rc<T></code> value has not been dropped yet and a result of <code>None</code> if the
|
||||
<code>Rc<T></code> value has been dropped. Because <code>upgrade</code> returns an <code>Option<Rc<T>></code>,
|
||||
Rust will ensure that the <code>Some</code> case and the <code>None</code> case are handled, and
|
||||
there won’t be an invalid pointer.</p>
|
||||
<p>As an example, rather than using a list whose items know only about the next
|
||||
item, we’ll create a tree whose items know about their child items <em>and</em> their
|
||||
parent items.</p>
|
||||
<!-- Old headings. Do not remove or links may break. -->
|
||||
<p><a id="creating-a-tree-data-structure-a-node-with-child-nodes"></a></p>
|
||||
<h4 id="creating-a-tree-data-structure"><a class="header" href="#creating-a-tree-data-structure">Creating a Tree Data Structure</a></h4>
|
||||
<p>To start, we’ll build a tree with nodes that know about their child nodes.
|
||||
We’ll create a struct named <code>Node</code> that holds its own <code>i32</code> value as well as
|
||||
references to its child <code>Node</code> values:</p>
|
||||
<p><span class="filename">Filename: src/main.rs</span></p>
|
||||
<pre class="playground"><code class="language-rust edition2024">use std::cell::RefCell;
|
||||
use std::rc::Rc;
|
||||
|
||||
#[derive(Debug)]
|
||||
struct Node {
|
||||
value: i32,
|
||||
children: RefCell<Vec<Rc<Node>>>,
|
||||
}
|
||||
<span class="boring">
|
||||
</span><span class="boring">fn main() {
|
||||
</span><span class="boring"> let leaf = Rc::new(Node {
|
||||
</span><span class="boring"> value: 3,
|
||||
</span><span class="boring"> children: RefCell::new(vec![]),
|
||||
</span><span class="boring"> });
|
||||
</span><span class="boring">
|
||||
</span><span class="boring"> let branch = Rc::new(Node {
|
||||
</span><span class="boring"> value: 5,
|
||||
</span><span class="boring"> children: RefCell::new(vec![Rc::clone(&leaf)]),
|
||||
</span><span class="boring"> });
|
||||
</span><span class="boring">}</span></code></pre>
|
||||
<p>We want a <code>Node</code> to own its children, and we want to share that ownership with
|
||||
variables so that we can access each <code>Node</code> in the tree directly. To do this,
|
||||
we define the <code>Vec<T></code> items to be values of type <code>Rc<Node></code>. We also want to
|
||||
modify which nodes are children of another node, so we have a <code>RefCell<T></code> in
|
||||
<code>children</code> around the <code>Vec<Rc<Node>></code>.</p>
|
||||
<p>Next, we’ll use our struct definition and create one <code>Node</code> instance named
|
||||
<code>leaf</code> with the value <code>3</code> and no children, and another instance named <code>branch</code>
|
||||
with the value <code>5</code> and <code>leaf</code> as one of its children, as shown in Listing 15-27.</p>
|
||||
<figure class="listing" id="listing-15-27">
|
||||
<span class="file-name">Filename: src/main.rs</span>
|
||||
<pre class="playground"><code class="language-rust edition2024"><span class="boring">use std::cell::RefCell;
|
||||
</span><span class="boring">use std::rc::Rc;
|
||||
</span><span class="boring">
|
||||
</span><span class="boring">#[derive(Debug)]
|
||||
</span><span class="boring">struct Node {
|
||||
</span><span class="boring"> value: i32,
|
||||
</span><span class="boring"> children: RefCell<Vec<Rc<Node>>>,
|
||||
</span><span class="boring">}
|
||||
</span><span class="boring">
|
||||
</span>fn main() {
|
||||
let leaf = Rc::new(Node {
|
||||
value: 3,
|
||||
children: RefCell::new(vec![]),
|
||||
});
|
||||
|
||||
let branch = Rc::new(Node {
|
||||
value: 5,
|
||||
children: RefCell::new(vec![Rc::clone(&leaf)]),
|
||||
});
|
||||
}</code></pre>
|
||||
<figcaption><a href="#listing-15-27">Listing 15-27</a>: Creating a <code>leaf</code> node with no children and a <code>branch</code> node with <code>leaf</code> as one of its children</figcaption>
|
||||
</figure>
|
||||
<p>We clone the <code>Rc<Node></code> in <code>leaf</code> and store that in <code>branch</code>, meaning the
|
||||
<code>Node</code> in <code>leaf</code> now has two owners: <code>leaf</code> and <code>branch</code>. We can get from
|
||||
<code>branch</code> to <code>leaf</code> through <code>branch.children</code>, but there’s no way to get from
|
||||
<code>leaf</code> to <code>branch</code>. The reason is that <code>leaf</code> has no reference to <code>branch</code> and
|
||||
doesn’t know they’re related. We want <code>leaf</code> to know that <code>branch</code> is its
|
||||
parent. We’ll do that next.</p>
|
||||
<h4 id="adding-a-reference-from-a-child-to-its-parent"><a class="header" href="#adding-a-reference-from-a-child-to-its-parent">Adding a Reference from a Child to Its Parent</a></h4>
|
||||
<p>To make the child node aware of its parent, we need to add a <code>parent</code> field to
|
||||
our <code>Node</code> struct definition. The trouble is in deciding what the type of
|
||||
<code>parent</code> should be. We know it can’t contain an <code>Rc<T></code>, because that would
|
||||
create a reference cycle with <code>leaf.parent</code> pointing to <code>branch</code> and
|
||||
<code>branch.children</code> pointing to <code>leaf</code>, which would cause their <code>strong_count</code>
|
||||
values to never be 0.</p>
|
||||
<p>Thinking about the relationships another way, a parent node should own its
|
||||
children: If a parent node is dropped, its child nodes should be dropped as
|
||||
well. However, a child should not own its parent: If we drop a child node, the
|
||||
parent should still exist. This is a case for weak references!</p>
|
||||
<p>So, instead of <code>Rc<T></code>, we’ll make the type of <code>parent</code> use <code>Weak<T></code>,
|
||||
specifically a <code>RefCell<Weak<Node>></code>. Now our <code>Node</code> struct definition looks
|
||||
like this:</p>
|
||||
<p><span class="filename">Filename: src/main.rs</span></p>
|
||||
<pre class="playground"><code class="language-rust edition2024">use std::cell::RefCell;
|
||||
use std::rc::{Rc, Weak};
|
||||
|
||||
#[derive(Debug)]
|
||||
struct Node {
|
||||
value: i32,
|
||||
parent: RefCell<Weak<Node>>,
|
||||
children: RefCell<Vec<Rc<Node>>>,
|
||||
}
|
||||
<span class="boring">
|
||||
</span><span class="boring">fn main() {
|
||||
</span><span class="boring"> let leaf = Rc::new(Node {
|
||||
</span><span class="boring"> value: 3,
|
||||
</span><span class="boring"> parent: RefCell::new(Weak::new()),
|
||||
</span><span class="boring"> children: RefCell::new(vec![]),
|
||||
</span><span class="boring"> });
|
||||
</span><span class="boring">
|
||||
</span><span class="boring"> println!("leaf parent = {:?}", leaf.parent.borrow().upgrade());
|
||||
</span><span class="boring">
|
||||
</span><span class="boring"> let branch = Rc::new(Node {
|
||||
</span><span class="boring"> value: 5,
|
||||
</span><span class="boring"> parent: RefCell::new(Weak::new()),
|
||||
</span><span class="boring"> children: RefCell::new(vec![Rc::clone(&leaf)]),
|
||||
</span><span class="boring"> });
|
||||
</span><span class="boring">
|
||||
</span><span class="boring"> *leaf.parent.borrow_mut() = Rc::downgrade(&branch);
|
||||
</span><span class="boring">
|
||||
</span><span class="boring"> println!("leaf parent = {:?}", leaf.parent.borrow().upgrade());
|
||||
</span><span class="boring">}</span></code></pre>
|
||||
<p>A node will be able to refer to its parent node but doesn’t own its parent. In
|
||||
Listing 15-28, we update <code>main</code> to use this new definition so that the <code>leaf</code>
|
||||
node will have a way to refer to its parent, <code>branch</code>.</p>
|
||||
<figure class="listing" id="listing-15-28">
|
||||
<span class="file-name">Filename: src/main.rs</span>
|
||||
<pre class="playground"><code class="language-rust edition2024"><span class="boring">use std::cell::RefCell;
|
||||
</span><span class="boring">use std::rc::{Rc, Weak};
|
||||
</span><span class="boring">
|
||||
</span><span class="boring">#[derive(Debug)]
|
||||
</span><span class="boring">struct Node {
|
||||
</span><span class="boring"> value: i32,
|
||||
</span><span class="boring"> parent: RefCell<Weak<Node>>,
|
||||
</span><span class="boring"> children: RefCell<Vec<Rc<Node>>>,
|
||||
</span><span class="boring">}
|
||||
</span><span class="boring">
|
||||
</span>fn main() {
|
||||
let leaf = Rc::new(Node {
|
||||
value: 3,
|
||||
parent: RefCell::new(Weak::new()),
|
||||
children: RefCell::new(vec![]),
|
||||
});
|
||||
|
||||
println!("leaf parent = {:?}", leaf.parent.borrow().upgrade());
|
||||
|
||||
let branch = Rc::new(Node {
|
||||
value: 5,
|
||||
parent: RefCell::new(Weak::new()),
|
||||
children: RefCell::new(vec![Rc::clone(&leaf)]),
|
||||
});
|
||||
|
||||
*leaf.parent.borrow_mut() = Rc::downgrade(&branch);
|
||||
|
||||
println!("leaf parent = {:?}", leaf.parent.borrow().upgrade());
|
||||
}</code></pre>
|
||||
<figcaption><a href="#listing-15-28">Listing 15-28</a>: A <code>leaf</code> node with a weak reference to its parent node, <code>branch</code></figcaption>
|
||||
</figure>
|
||||
<p>Creating the <code>leaf</code> node looks similar to Listing 15-27 with the exception of
|
||||
the <code>parent</code> field: <code>leaf</code> starts out without a parent, so we create a new,
|
||||
empty <code>Weak<Node></code> reference instance.</p>
|
||||
<p>At this point, when we try to get a reference to the parent of <code>leaf</code> by using
|
||||
the <code>upgrade</code> method, we get a <code>None</code> value. We see this in the output from the
|
||||
first <code>println!</code> statement:</p>
|
||||
<pre><code class="language-text">leaf parent = None
|
||||
</code></pre>
|
||||
<p>When we create the <code>branch</code> node, it will also have a new <code>Weak<Node></code>
|
||||
reference in the <code>parent</code> field because <code>branch</code> doesn’t have a parent node. We
|
||||
still have <code>leaf</code> as one of the children of <code>branch</code>. Once we have the <code>Node</code>
|
||||
instance in <code>branch</code>, we can modify <code>leaf</code> to give it a <code>Weak<Node></code> reference
|
||||
to its parent. We use the <code>borrow_mut</code> method on the <code>RefCell<Weak<Node>></code> in
|
||||
the <code>parent</code> field of <code>leaf</code>, and then we use the <code>Rc::downgrade</code> function to
|
||||
create a <code>Weak<Node></code> reference to <code>branch</code> from the <code>Rc<Node></code> in <code>branch</code>.</p>
|
||||
<p>When we print the parent of <code>leaf</code> again, this time we’ll get a <code>Some</code> variant
|
||||
holding <code>branch</code>: Now <code>leaf</code> can access its parent! When we print <code>leaf</code>, we
|
||||
also avoid the cycle that eventually ended in a stack overflow like we had in
|
||||
Listing 15-26; the <code>Weak<Node></code> references are printed as <code>(Weak)</code>:</p>
|
||||
<pre><code class="language-text">leaf parent = Some(Node { value: 5, parent: RefCell { value: (Weak) },
|
||||
children: RefCell { value: [Node { value: 3, parent: RefCell { value: (Weak) },
|
||||
children: RefCell { value: [] } }] } })
|
||||
</code></pre>
|
||||
<p>The lack of infinite output indicates that this code didn’t create a reference
|
||||
cycle. We can also tell this by looking at the values we get from calling
|
||||
<code>Rc::strong_count</code> and <code>Rc::weak_count</code>.</p>
|
||||
<h4 id="visualizing-changes-to-strong_count-and-weak_count"><a class="header" href="#visualizing-changes-to-strong_count-and-weak_count">Visualizing Changes to <code>strong_count</code> and <code>weak_count</code></a></h4>
|
||||
<p>Let’s look at how the <code>strong_count</code> and <code>weak_count</code> values of the <code>Rc<Node></code>
|
||||
instances change by creating a new inner scope and moving the creation of
|
||||
<code>branch</code> into that scope. By doing so, we can see what happens when <code>branch</code> is
|
||||
created and then dropped when it goes out of scope. The modifications are shown
|
||||
in Listing 15-29.</p>
|
||||
<figure class="listing" id="listing-15-29">
|
||||
<span class="file-name">Filename: src/main.rs</span>
|
||||
<pre class="playground"><code class="language-rust edition2024"><span class="boring">use std::cell::RefCell;
|
||||
</span><span class="boring">use std::rc::{Rc, Weak};
|
||||
</span><span class="boring">
|
||||
</span><span class="boring">#[derive(Debug)]
|
||||
</span><span class="boring">struct Node {
|
||||
</span><span class="boring"> value: i32,
|
||||
</span><span class="boring"> parent: RefCell<Weak<Node>>,
|
||||
</span><span class="boring"> children: RefCell<Vec<Rc<Node>>>,
|
||||
</span><span class="boring">}
|
||||
</span><span class="boring">
|
||||
</span>fn main() {
|
||||
let leaf = Rc::new(Node {
|
||||
value: 3,
|
||||
parent: RefCell::new(Weak::new()),
|
||||
children: RefCell::new(vec![]),
|
||||
});
|
||||
|
||||
println!(
|
||||
"leaf strong = {}, weak = {}",
|
||||
Rc::strong_count(&leaf),
|
||||
Rc::weak_count(&leaf),
|
||||
);
|
||||
|
||||
{
|
||||
let branch = Rc::new(Node {
|
||||
value: 5,
|
||||
parent: RefCell::new(Weak::new()),
|
||||
children: RefCell::new(vec![Rc::clone(&leaf)]),
|
||||
});
|
||||
|
||||
*leaf.parent.borrow_mut() = Rc::downgrade(&branch);
|
||||
|
||||
println!(
|
||||
"branch strong = {}, weak = {}",
|
||||
Rc::strong_count(&branch),
|
||||
Rc::weak_count(&branch),
|
||||
);
|
||||
|
||||
println!(
|
||||
"leaf strong = {}, weak = {}",
|
||||
Rc::strong_count(&leaf),
|
||||
Rc::weak_count(&leaf),
|
||||
);
|
||||
}
|
||||
|
||||
println!("leaf parent = {:?}", leaf.parent.borrow().upgrade());
|
||||
println!(
|
||||
"leaf strong = {}, weak = {}",
|
||||
Rc::strong_count(&leaf),
|
||||
Rc::weak_count(&leaf),
|
||||
);
|
||||
}</code></pre>
|
||||
<figcaption><a href="#listing-15-29">Listing 15-29</a>: Creating <code>branch</code> in an inner scope and examining strong and weak reference counts</figcaption>
|
||||
</figure>
|
||||
<p>After <code>leaf</code> is created, its <code>Rc<Node></code> has a strong count of 1 and a weak
|
||||
count of 0. In the inner scope, we create <code>branch</code> and associate it with
|
||||
<code>leaf</code>, at which point when we print the counts, the <code>Rc<Node></code> in <code>branch</code>
|
||||
will have a strong count of 1 and a weak count of 1 (for <code>leaf.parent</code> pointing
|
||||
to <code>branch</code> with a <code>Weak<Node></code>). When we print the counts in <code>leaf</code>, we’ll see
|
||||
it will have a strong count of 2 because <code>branch</code> now has a clone of the
|
||||
<code>Rc<Node></code> of <code>leaf</code> stored in <code>branch.children</code> but will still have a weak
|
||||
count of 0.</p>
|
||||
<p>When the inner scope ends, <code>branch</code> goes out of scope and the strong count of
|
||||
the <code>Rc<Node></code> decreases to 0, so its <code>Node</code> is dropped. The weak count of 1
|
||||
from <code>leaf.parent</code> has no bearing on whether or not <code>Node</code> is dropped, so we
|
||||
don’t get any memory leaks!</p>
|
||||
<p>If we try to access the parent of <code>leaf</code> after the end of the scope, we’ll get
|
||||
<code>None</code> again. At the end of the program, the <code>Rc<Node></code> in <code>leaf</code> has a strong
|
||||
count of 1 and a weak count of 0 because the variable <code>leaf</code> is now the only
|
||||
reference to the <code>Rc<Node></code> again.</p>
|
||||
<p>All of the logic that manages the counts and value dropping is built into
|
||||
<code>Rc<T></code> and <code>Weak<T></code> and their implementations of the <code>Drop</code> trait. By
|
||||
specifying that the relationship from a child to its parent should be a
|
||||
<code>Weak<T></code> reference in the definition of <code>Node</code>, you’re able to have parent
|
||||
nodes point to child nodes and vice versa without creating a reference cycle
|
||||
and memory leaks.</p>
|
||||
<h2 id="summary"><a class="header" href="#summary">Summary</a></h2>
|
||||
<p>This chapter covered how to use smart pointers to make different guarantees and
|
||||
trade-offs from those Rust makes by default with regular references. The
|
||||
<code>Box<T></code> type has a known size and points to data allocated on the heap. The
|
||||
<code>Rc<T></code> type keeps track of the number of references to data on the heap so
|
||||
that the data can have multiple owners. The <code>RefCell<T></code> type with its interior
|
||||
mutability gives us a type that we can use when we need an immutable type but
|
||||
need to change an inner value of that type; it also enforces the borrowing
|
||||
rules at runtime instead of at compile time.</p>
|
||||
<p>Also discussed were the <code>Deref</code> and <code>Drop</code> traits, which enable a lot of the
|
||||
functionality of smart pointers. We explored reference cycles that can cause
|
||||
memory leaks and how to prevent them using <code>Weak<T></code>.</p>
|
||||
<p>If this chapter has piqued your interest and you want to implement your own
|
||||
smart pointers, check out <a href="../nomicon/index.html">“The Rustonomicon”</a> for more useful
|
||||
information.</p>
|
||||
<p>Next, we’ll talk about concurrency in Rust. You’ll even learn about a few new
|
||||
smart pointers.</p>
|
||||
|
||||
</main>
|
||||
|
||||
<nav class="nav-wrapper" aria-label="Page navigation">
|
||||
<!-- Mobile navigation buttons -->
|
||||
<a rel="prev" href="ch15-05-interior-mutability.html" class="mobile-nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 320 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M41.4 233.4c-12.5 12.5-12.5 32.8 0 45.3l160 160c12.5 12.5 32.8 12.5 45.3 0s12.5-32.8 0-45.3L109.3 256 246.6 118.6c12.5-12.5 12.5-32.8 0-45.3s-32.8-12.5-45.3 0l-160 160z"/></svg></span>
|
||||
</a>
|
||||
|
||||
<a rel="next prefetch" href="ch16-00-concurrency.html" class="mobile-nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 320 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M278.6 233.4c12.5 12.5 12.5 32.8 0 45.3l-160 160c-12.5 12.5-32.8 12.5-45.3 0s-12.5-32.8 0-45.3L210.7 256 73.4 118.6c-12.5-12.5-12.5-32.8 0-45.3s32.8-12.5 45.3 0l160 160z"/></svg></span>
|
||||
</a>
|
||||
|
||||
<div style="clear: both"></div>
|
||||
</nav>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<nav class="nav-wide-wrapper" aria-label="Page navigation">
|
||||
<a rel="prev" href="ch15-05-interior-mutability.html" class="nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 320 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M41.4 233.4c-12.5 12.5-12.5 32.8 0 45.3l160 160c12.5 12.5 32.8 12.5 45.3 0s12.5-32.8 0-45.3L109.3 256 246.6 118.6c12.5-12.5 12.5-32.8 0-45.3s-32.8-12.5-45.3 0l-160 160z"/></svg></span>
|
||||
</a>
|
||||
|
||||
<a rel="next prefetch" href="ch16-00-concurrency.html" class="nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
|
||||
<span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 320 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M278.6 233.4c12.5 12.5 12.5 32.8 0 45.3l-160 160c-12.5 12.5-32.8 12.5-45.3 0s-12.5-32.8 0-45.3L210.7 256 73.4 118.6c-12.5-12.5-12.5-32.8 0-45.3s32.8-12.5 45.3 0l160 160z"/></svg></span>
|
||||
</a>
|
||||
</nav>
|
||||
|
||||
</div>
|
||||
|
||||
<template id=fa-eye><span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M288 32c-80.8 0-145.5 36.8-192.6 80.6C48.6 156 17.3 208 2.5 243.7c-3.3 7.9-3.3 16.7 0 24.6C17.3 304 48.6 356 95.4 399.4C142.5 443.2 207.2 480 288 480s145.5-36.8 192.6-80.6c46.8-43.5 78.1-95.4 93-131.1c3.3-7.9 3.3-16.7 0-24.6c-14.9-35.7-46.2-87.7-93-131.1C433.5 68.8 368.8 32 288 32zM432 256c0 79.5-64.5 144-144 144s-144-64.5-144-144s64.5-144 144-144s144 64.5 144 144zM288 192c0 35.3-28.7 64-64 64c-11.5 0-22.3-3-31.6-8.4c-.2 2.8-.4 5.5-.4 8.4c0 53 43 96 96 96s96-43 96-96s-43-96-96-96c-2.8 0-5.6 .1-8.4 .4c5.3 9.3 8.4 20.1 8.4 31.6z"/></svg></span></template>
|
||||
<template id=fa-eye-slash><span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M38.8 5.1C28.4-3.1 13.3-1.2 5.1 9.2S-1.2 34.7 9.2 42.9l592 464c10.4 8.2 25.5 6.3 33.7-4.1s6.3-25.5-4.1-33.7L525.6 386.7c39.6-40.6 66.4-86.1 79.9-118.4c3.3-7.9 3.3-16.7 0-24.6c-14.9-35.7-46.2-87.7-93-131.1C465.5 68.8 400.8 32 320 32c-68.2 0-125 26.3-169.3 60.8L38.8 5.1zM223.1 149.5C248.6 126.2 282.7 112 320 112c79.5 0 144 64.5 144 144c0 24.9-6.3 48.3-17.4 68.7L408 294.5c5.2-11.8 8-24.8 8-38.5c0-53-43-96-96-96c-2.8 0-5.6 .1-8.4 .4c5.3 9.3 8.4 20.1 8.4 31.6c0 10.2-2.4 19.8-6.6 28.3l-90.3-70.8zm223.1 298L373 389.9c-16.4 6.5-34.3 10.1-53 10.1c-79.5 0-144-64.5-144-144c0-6.9 .5-13.6 1.4-20.2L83.1 161.5C60.3 191.2 44 220.8 34.5 243.7c-3.3 7.9-3.3 16.7 0 24.6c14.9 35.7 46.2 87.7 93 131.1C174.5 443.2 239.2 480 320 480c47.8 0 89.9-12.9 126.2-32.5z"/></svg></span></template>
|
||||
<template id=fa-copy><span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M502.6 70.63l-61.25-61.25C435.4 3.371 427.2 0 418.7 0H255.1c-35.35 0-64 28.66-64 64l.0195 256C192 355.4 220.7 384 256 384h192c35.2 0 64-28.8 64-64V93.25C512 84.77 508.6 76.63 502.6 70.63zM464 320c0 8.836-7.164 16-16 16H255.1c-8.838 0-16-7.164-16-16L239.1 64.13c0-8.836 7.164-16 16-16h128L384 96c0 17.67 14.33 32 32 32h47.1V320zM272 448c0 8.836-7.164 16-16 16H63.1c-8.838 0-16-7.164-16-16L47.98 192.1c0-8.836 7.164-16 16-16H160V128H63.99c-35.35 0-64 28.65-64 64l.0098 256C.002 483.3 28.66 512 64 512h192c35.2 0 64-28.8 64-64v-32h-47.1L272 448z"/></svg></span></template>
|
||||
<template id=fa-play><span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 384 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M73 39c-14.8-9.1-33.4-9.4-48.5-.9S0 62.6 0 80V432c0 17.4 9.4 33.4 24.5 41.9s33.7 8.1 48.5-.9L361 297c14.3-8.7 23-24.2 23-41s-8.7-32.2-23-41L73 39z"/></svg></span></template>
|
||||
<template id=fa-clock-rotate-left><span class=fa-svg><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 6.2.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2022 Fonticons, Inc. --><path d="M75 75L41 41C25.9 25.9 0 36.6 0 57.9V168c0 13.3 10.7 24 24 24H134.1c21.4 0 32.1-25.9 17-41l-30.8-30.8C155 85.5 203 64 256 64c106 0 192 86 192 192s-86 192-192 192c-40.8 0-78.6-12.7-109.7-34.4c-14.5-10.1-34.4-6.6-44.6 7.9s-6.6 34.4 7.9 44.6C151.2 495 201.7 512 256 512c141.4 0 256-114.6 256-256S397.4 0 256 0C185.3 0 121.3 28.7 75 75zm181 53c-13.3 0-24 10.7-24 24V256c0 6.4 2.5 12.5 7 17l72 72c9.4 9.4 24.6 9.4 33.9 0s9.4-24.6 0-33.9l-65-65V152c0-13.3-10.7-24-24-24z"/></svg></span></template>
|
||||
|
||||
|
||||
|
||||
<script>
|
||||
window.playground_copyable = true;
|
||||
</script>
|
||||
|
||||
|
||||
<script src="elasticlunr-ef4e11c1.min.js"></script>
|
||||
<script src="mark-09e88c2c.min.js"></script>
|
||||
<script src="searcher-09f2665d.js"></script>
|
||||
|
||||
<script src="clipboard-1626706a.min.js"></script>
|
||||
<script src="highlight-abc7f01d.js"></script>
|
||||
<script src="book-c22b7243.js"></script>
|
||||
|
||||
<!-- Custom JS scripts -->
|
||||
<script src="ferris-2317480c.js"></script>
|
||||
|
||||
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
Reference in New Issue
Block a user