|
|
<!DOCTYPE HTML>
|
|
|
<html lang="en" class="light" dir="ltr">
|
|
|
<head>
|
|
|
<!-- Book generated using mdBook -->
|
|
|
<meta charset="UTF-8">
|
|
|
<title>RefCell<T> 与内部可变性模式 - Rust 程序设计语言 简体中文版</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.svg">
|
|
|
<link rel="shortcut icon" href="favicon.png">
|
|
|
<link rel="stylesheet" href="css/variables.css">
|
|
|
<link rel="stylesheet" href="css/general.css">
|
|
|
<link rel="stylesheet" href="css/chrome.css">
|
|
|
<link rel="stylesheet" href="css/print.css" media="print">
|
|
|
|
|
|
<!-- Fonts -->
|
|
|
<link rel="stylesheet" href="FontAwesome/css/font-awesome.css">
|
|
|
<link rel="stylesheet" href="fonts/fonts.css">
|
|
|
|
|
|
<!-- Highlight.js Stylesheets -->
|
|
|
<link rel="stylesheet" href="highlight.css">
|
|
|
<link rel="stylesheet" href="tomorrow-night.css">
|
|
|
<link rel="stylesheet" href="ayu-highlight.css">
|
|
|
|
|
|
<!-- Custom theme stylesheets -->
|
|
|
<link rel="stylesheet" href="ferris.css">
|
|
|
<link rel="stylesheet" href="theme/2018-edition.css">
|
|
|
<link rel="stylesheet" href="theme/semantic-notes.css">
|
|
|
<link rel="stylesheet" href="theme/listing.css">
|
|
|
|
|
|
</head>
|
|
|
<body class="sidebar-visible no-js">
|
|
|
<div id="body-container">
|
|
|
<!-- Provide site root to javascript -->
|
|
|
<script>
|
|
|
var path_to_root = "";
|
|
|
var default_theme = window.matchMedia("(prefers-color-scheme: dark)").matches ? "navy" : "light";
|
|
|
</script>
|
|
|
|
|
|
<!-- Work around some values being stored in localStorage wrapped in quotes -->
|
|
|
<script>
|
|
|
try {
|
|
|
var theme = localStorage.getItem('mdbook-theme');
|
|
|
var 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>
|
|
|
var theme;
|
|
|
try { theme = localStorage.getItem('mdbook-theme'); } catch(e) { }
|
|
|
if (theme === null || theme === undefined) { theme = default_theme; }
|
|
|
var html = document.querySelector('html');
|
|
|
html.classList.remove('light')
|
|
|
html.classList.add(theme);
|
|
|
var body = document.querySelector('body');
|
|
|
body.classList.remove('no-js')
|
|
|
body.classList.add('js');
|
|
|
</script>
|
|
|
|
|
|
<input type="checkbox" id="sidebar-toggle-anchor" class="hidden">
|
|
|
|
|
|
<!-- Hide / unhide sidebar before it is displayed -->
|
|
|
<script>
|
|
|
var body = document.querySelector('body');
|
|
|
var sidebar = null;
|
|
|
var sidebar_toggle = document.getElementById("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 = sidebar === 'visible';
|
|
|
body.classList.remove('sidebar-visible');
|
|
|
body.classList.add("sidebar-" + sidebar);
|
|
|
</script>
|
|
|
|
|
|
<nav id="sidebar" class="sidebar" aria-label="Table of contents">
|
|
|
<div class="sidebar-scrollbox">
|
|
|
<ol class="chapter"><li class="chapter-item expanded affix "><a href="title-page.html">Rust 程序设计语言</a></li><li class="chapter-item expanded affix "><a href="foreword.html">前言</a></li><li class="chapter-item expanded affix "><a href="ch00-00-introduction.html">简介</a></li><li class="chapter-item expanded "><a href="ch01-00-getting-started.html"><strong aria-hidden="true">1.</strong> 入门指南</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch01-01-installation.html"><strong aria-hidden="true">1.1.</strong> 安装</a></li><li class="chapter-item expanded "><a href="ch01-02-hello-world.html"><strong aria-hidden="true">1.2.</strong> Hello, World!</a></li><li class="chapter-item expanded "><a href="ch01-03-hello-cargo.html"><strong aria-hidden="true">1.3.</strong> Hello, Cargo!</a></li></ol></li><li class="chapter-item expanded "><a href="ch02-00-guessing-game-tutorial.html"><strong aria-hidden="true">2.</strong> 写个猜数字游戏</a></li><li class="chapter-item expanded "><a href="ch03-00-common-programming-concepts.html"><strong aria-hidden="true">3.</strong> 常见编程概念</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch03-01-variables-and-mutability.html"><strong aria-hidden="true">3.1.</strong> 变量与可变性</a></li><li class="chapter-item expanded "><a href="ch03-02-data-types.html"><strong aria-hidden="true">3.2.</strong> 数据类型</a></li><li class="chapter-item expanded "><a href="ch03-03-how-functions-work.html"><strong aria-hidden="true">3.3.</strong> 函数</a></li><li class="chapter-item expanded "><a href="ch03-04-comments.html"><strong aria-hidden="true">3.4.</strong> 注释</a></li><li class="chapter-item expanded "><a href="ch03-05-control-flow.html"><strong aria-hidden="true">3.5.</strong> 控制流</a></li></ol></li><li class="chapter-item expanded "><a href="ch04-00-understanding-ownership.html"><strong aria-hidden="true">4.</strong> 认识所有权</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch04-01-what-is-ownership.html"><strong aria-hidden="true">4.1.</strong> 什么是所有权？</a></li><li class="chapter-item expanded "><a href="ch04-02-references-and-borrowing.html"><strong aria-hidden="true">4.2.</strong> 引用与借用</a></li><li class="chapter-item expanded "><a href="ch04-03-slices.html"><strong aria-hidden="true">4.3.</strong> Slice 类型</a></li></ol></li><li class="chapter-item expanded "><a href="ch05-00-structs.html"><strong aria-hidden="true">5.</strong> 使用结构体组织相关联的数据</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch05-01-defining-structs.html"><strong aria-hidden="true">5.1.</strong> 结构体的定义和实例化</a></li><li class="chapter-item expanded "><a href="ch05-02-example-structs.html"><strong aria-hidden="true">5.2.</strong> 结构体示例程序</a></li><li class="chapter-item expanded "><a href="ch05-03-method-syntax.html"><strong aria-hidden="true">5.3.</strong> 方法语法</a></li></ol></li><li class="chapter-item expanded "><a href="ch06-00-enums.html"><strong aria-hidden="true">6.</strong> 枚举和模式匹配</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch06-01-defining-an-enum.html"><strong aria-hidden="true">6.1.</strong> 枚举的定义</a></li><li class="chapter-item expanded "><a href="ch06-02-match.html"><strong aria-hidden="true">6.2.</strong> match 控制流结构</a></li><li class="chapter-item expanded "><a href="ch06-03-if-let.html"><strong aria-hidden="true">6.3.</strong> if let 简洁控制流</a></li></ol></li><li class="chapter-item expanded "><a href="ch07-00-managing-growing-projects-with-packages-crates-and-modules.html"><strong aria-hidden="true">7.</strong> 使用包、Crate 和模块管理不断增长的项目</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch07-01-packages-and-crates.html"><strong aria-hidden="true">7.1.</strong> 包和 Crate</a></li><li class="chapter-item expanded "><a href="ch07-02-defining-modules-to-control-scope-and-privacy.html"><strong aria-hidden="true">7.2.</strong> 定义模块来控制作用域与私有性</a></li><li class="chapter-item expanded "><a href="ch07-03-paths-for-referring-to-an-item-in-the-module-tree.html"><strong aria-hidden="true">7.3.</strong> 引用模块项目的路径</a></li><li class="chapter-item expanded "><a href="ch07-04-bringing-paths-into-scope-with-the-use-keyword.html"><strong aria-hidden="true">7.4.</strong> 使用 use 关键字将路径引入作用域</a></li><li class="chapter-item expanded "><a href="ch07-05-separating-modules-into-different-files.html"><strong aria-hidden="true">7.5.</strong> 将模块拆分成多个文件</a></li></ol></li><li class="chapter-item expanded "><a href="ch08-00-common-collections.html"><strong aria-hidden="true">8.</strong> 常见集合</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch08-01-vectors.html"><strong aria-hidden="true">8.1.</strong> 使用 Vector 储存列表</a></li><li class="chapter-item expanded "><a href="ch08-02-strings.html"><strong aria-hidden="true">8.2.</strong> 使用字符串储存 UTF-8 编码的文本</a></li><li class="chapter-item expanded "><a href="ch08-03-hash-maps.html"><strong aria-hidden="true">8.3.</strong> 使用 Hash Map 储存键值对</a></li></ol></li><li class="chapter-item expanded "><a href="ch09-00-error-handling.html"><strong aria-hidden="true">9.</strong> 错误处理</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch09-01-unrecoverable-errors-with-panic.html"><strong aria-hidden="true">9.1.</strong> 用 panic! 处理不可恢复的错误</a></li><li class="chapter-item expanded "><a href="ch09-02-recoverable-errors-with-result.html"><strong aria-hidden="true">9.2.</strong> 用 Result 处理可恢复的错误</a></li><li class="chapter-item expanded "><a href="ch09-03-to-panic-or-not-to-panic.html"><strong aria-hidden="true">9.3.</strong> 要不要 panic!</a></li></ol></li><li class="chapter-item expanded "><a href="ch10-00-generics.html"><strong aria-hidden="true">10.</strong> 泛型、Trait 和生命周期</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch10-01-syntax.html"><strong aria-hidden="true">10.1.</strong> 泛型数据类型</a></li><li class="chapter-item expanded "><a href="ch10-02-traits.html"><strong aria-hidden="true">10.2.</strong> Trait：定义共同行为</a></li><li class="chapter-item expanded "><a href="ch10-03-lifetime-syntax.html"><strong aria-hidden="true">10.3.</strong> 生命周期确保引用有效</a></li></ol></li><li class="chapter-item expanded "><a href="ch11-00-testing.html"><strong aria-hidden="true">11.</strong> 编写自动化测试</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch11-01-writing-tests.html"><strong aria-hidden="true">11.1.</strong> 如何编写测试</a></li><li class="chapter-item expanded "><a href="ch11-02-running-tests.html"><strong aria-hidden="true">11.2.</strong> 控制测试如何运行</a></li><li class="chapter-item expanded "><a href="ch11-03-test-organization.html"><strong aria-hidden="true">11.3.</strong> 测试的组织结构</a></li></ol></li><li class="chapter-item expanded "><a href="ch12-00-an-io-project.html"><strong aria-hidden="true">12.</strong> 一个 I/O 项目：构建命令行程序</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch12-01-accepting-command-line-arguments.html"><strong aria-hidden="true">12.1.</strong> 接受命令行参数</a></li><li class="chapter-item expanded "><a href="ch12-02-reading-a-file.html"><strong aria-hidden="true">12.2.</strong> 读取文件</a></li><li class="chapter-item expanded "><a href="ch12-03-improving-error-handling-and-modularity.html"><strong aria-hidden="true">12.3.</strong> 重构以改进模块化与错误处理</a></li><li class="chapter-item expanded "><a href="ch12-04-testing-the-librarys-functionality.html"><strong aria-hidden="true">12.4.</strong> 采用测试驱动开发完善库的功能</a></li><li class="chapter-item expanded "><a href="ch12-05-working-with-environment-variables.html"><strong aria-hidden="true">12.5.</strong> 处理环境变量</a></li><li class="chapter-item expanded "><a href="ch12-06-writing-to-stderr-instead-of-stdout.html"><strong aria-hidden="true">12.6.</strong> 将错误信息输出到标准错误而不是标准输出</a></li></ol></li><li class="chapter-item expanded "><a href="ch13-00-functional-features.html"><strong aria-hidden="true">13.</strong> Rust 中的函数式语言功能：迭代器与闭包</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch13-01-closures.html"><strong aria-hidden="true">13.1.</strong> 闭包：可以捕获其环境的匿名函数</a></li><li class="chapter-item expanded "><a href="ch13-02-iterators.html"><strong aria-hidden="true">13.2.</strong> 使用迭代器处理元素序列</a></li><li class="chapter-item expanded "><a href="ch13-03-improving-our-io-project.html"><strong aria-hidden="true">13.3.</strong> 改进之前的 I/O 项目</a></li><li class="chapter-item expanded "><a href="ch13-04-performance.html"><strong aria-hidden="true">13.4.</strong> 性能比较：循环对迭代器</a></li></ol></li><li class="chapter-item expanded "><a href="ch14-00-more-about-cargo.html"><strong aria-hidden="true">14.</strong> 更多关于 Cargo 和 Crates.io 的内容</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch14-01-release-profiles.html"><strong aria-hidden="true">14.1.</strong> 采用发布配置自定义构建</a></li><li class="chapter-item expanded "><a href="ch14-02-publishing-to-crates-io.html"><strong aria-hidden="true">14.2.</strong> 将 crate 发布到 Crates.io</a></li><li class="chapter-item expanded "><a href="ch14-03-cargo-workspaces.html"><strong aria-hidden="true">14.3.</strong> Cargo 工作空间</a></li><li class="chapter-item expanded "><a href="ch14-04-installing-binaries.html"><strong aria-hidden="true">14.4.</strong> 使用 cargo install 安装二进制文件</a></li><li class="chapter-item expanded "><a href="ch14-05-extending-cargo.html"><strong aria-hidden="true">14.5.</strong> Cargo 自定义扩展命令</a></li></ol></li><li class="chapter-item expanded "><a href="ch15-00-smart-pointers.html"><strong aria-hidden="true">15.</strong> 智能指针</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch15-01-box.html"><strong aria-hidden="true">15.1.</strong> 使用 Box<T> 指向堆上数据</a></li><li class="chapter-item expanded "><a href="ch15-02-deref.html"><strong aria-hidden="true">15.2.</strong> 使用 Deref Trait 将智能指针当作常规引用处理</a></li><li class="chapter-item expanded "><a href="ch15-03-drop.html"><strong aria-hidden="true">15.3.</strong> 使用 Drop Trait 运行清理代码</a></li><li class="chapter-item expanded "><a href="ch15-04-rc.html"><strong aria-hidden="true">15.4.</strong> Rc<T> 引用计数智能指针</a></li><li class="chapter-item expanded "><a href="ch15-05-interior-mutability.html" class="active"><strong aria-hidden="true">15.5.</strong> RefCell<T> 与内部可变性模式</a></li><li class="chapter-item expanded "><a href="ch15-06-reference-cycles.html"><strong aria-hidden="true">15.6.</strong> 引用循环会导致内存泄漏</a></li></ol></li><li class="chapter-item expanded "><a href="ch16-00-concurrency.html"><strong aria-hidden="true">16.</strong> 无畏并发</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch16-01-threads.html"><strong aria-hidden="true">16.1.</strong> 使用线程同时地运行代码</a></li><li class="chapter-item expanded "><a href="ch16-02-message-passing.html"><strong aria-hidden="true">16.2.</strong> 使用消息传递在线程间通信</a></li><li class="chapter-item expanded "><a href="ch16-03-shared-state.html"><strong aria-hidden="true">16.3.</strong> 共享状态并发</a></li><li class="chapter-item expanded "><a href="ch16-04-extensible-concurrency-sync-and-send.html"><strong aria-hidden="true">16.4.</strong> 使用 Sync 与 Send Traits 的可扩展并发</a></li></ol></li><li class="chapter-item expanded "><a href="ch17-00-async-await.html"><strong aria-hidden="true">17.</strong> Async 和 await</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch17-01-futures-and-syntax.html"><strong aria-hidden="true">17.1.</strong> Futures 和 async 语法</a></li><li class="chapter-item expanded "><a href="ch17-02-concurrency-with-async.html"><strong aria-hidden="true">17.2.</strong> 并发与 async</a></li><li class="chapter-item expanded "><a href="ch17-03-more-futures.html"><strong aria-hidden="true">17.3.</strong> 使用任意数量的 futures</a></li><li class="chapter-item expanded "><a href="ch17-04-streams.html"><strong aria-hidden="true">17.4.</strong> 流（Streams）</a></li><li class="chapter-item expanded "><a href="ch17-05-traits-for-async.html"><strong aria-hidden="true">17.5.</strong> 深入理解 async 相关的 traits</a></li><li class="chapter-item expanded "><a href="ch17-06-futures-tasks-threads.html"><strong aria-hidden="true">17.6.</strong> Futures，任务（tasks）和线程（threads）</a></li></ol></li><li class="chapter-item expanded "><a href="ch18-00-oop.html"><strong aria-hidden="true">18.</strong> Rust 的面向对象编程特性</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch18-01-what-is-oo.html"><strong aria-hidden="true">18.1.</strong> 面向对象语言的特点</a></li><li class="chapter-item expanded "><a href="ch18-02-trait-objects.html"><strong aria-hidden="true">18.2.</strong> 顾及不同类型值的 trait 对象</a></li><li class="chapter-item expanded "><a href="ch18-03-oo-design-patterns.html"><strong aria-hidden="true">18.3.</strong> 面向对象设计模式的实现</a></li></ol></li><li class="chapter-item expanded "><a href="ch19-00-patterns.html"><strong aria-hidden="true">19.</strong> 模式与模式匹配</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch19-01-all-the-places-for-patterns.html"><strong aria-hidden="true">19.1.</strong> 所有可能会用到模式的位置</a></li><li class="chapter-item expanded "><a href="ch19-02-refutability.html"><strong aria-hidden="true">19.2.</strong> Refutability（可反驳性）: 模式是否会匹配失效</a></li><li class="chapter-item expanded "><a href="ch19-03-pattern-syntax.html"><strong aria-hidden="true">19.3.</strong> 模式语法</a></li></ol></li><li class="chapter-item expanded "><a href="ch20-00-advanced-features.html"><strong aria-hidden="true">20.</strong> 高级特征</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch20-01-unsafe-rust.html"><strong aria-hidden="true">20.1.</strong> 不安全的 Rust</a></li><li class="chapter-item expanded "><a href="ch20-03-advanced-traits.html"><strong aria-hidden="true">20.2.</strong> 高级 trait</a></li><li class="chapter-item expanded "><a href="ch20-04-advanced-types.html"><strong aria-hidden="true">20.3.</strong> 高级类型</a></li><li class="chapter-item expanded "><a href="ch20-05-advanced-functions-and-closures.html"><strong aria-hidden="true">20.4.</strong> 高级函数与闭包</a></li><li class="chapter-item expanded "><a href="ch20-06-macros.html"><strong aria-hidden="true">20.5.</strong> 宏</a></li></ol></li><li class="chapter-item expanded "><a href="ch21-00-final-project-a-web-server.html"><strong aria-hidden="true">21.</strong> 最后的项目：构建多线程 web server</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="ch21-01-single-threaded.html"><strong aria-hidden="true">21.1.</strong> 建立单线程 web server</a></li><li class="chapter-item expanded "><a href="ch21-02-multithreaded.html"><strong aria-hidden="true">21.2.</strong> 将单线程 server 变为多线程 server</a></li><li class="chapter-item expanded "><a href="ch21-03-graceful-shutdown-and-cleanup.html"><strong aria-hidden="true">21.3.</strong> 优雅停机与清理</a></li></ol></li><li class="chapter-item expanded "><a href="appendix-00.html"><strong aria-hidden="true">22.</strong> 附录</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="appendix-01-keywords.html"><strong aria-hidden="true">22.1.</strong> A - 关键字</a></li><li class="chapter-item expanded "><a href="appendix-02-operators.html"><strong aria-hidden="true">22.2.</strong> B - 运算符与符号</a></li><li class="chapter-item expanded "><a href="appendix-03-derivable-traits.html"><strong aria-hidden="true">22.3.</strong> C - 可派生的 trait</a></li><li class="chapter-item expanded "><a href="appendix-04-useful-development-tools.html"><strong aria-hidden="true">22.4.</strong> D - 实用开发工具</a></li><li class="chapter-item expanded "><a href="appendix-05-editions.html"><strong aria-hidden="true">22.5.</strong> E - 版本</a></li><li class="chapter-item expanded "><a href="appendix-06-translation.html"><strong aria-hidden="true">22.6.</strong> F - 本书译本</a></li><li class="chapter-item expanded "><a href="appendix-07-nightly-rust.html"><strong aria-hidden="true">22.7.</strong> G - Rust 是如何开发的与 “Nightly Rust”</a></li></ol></li></ol>
|
|
|
</div>
|
|
|
<div id="sidebar-resize-handle" class="sidebar-resize-handle">
|
|
|
<div class="sidebar-resize-indicator"></div>
|
|
|
</div>
|
|
|
</nav>
|
|
|
|
|
|
<!-- Track and set sidebar scroll position -->
|
|
|
<script>
|
|
|
var sidebarScrollbox = document.querySelector('#sidebar .sidebar-scrollbox');
|
|
|
sidebarScrollbox.addEventListener('click', function(e) {
|
|
|
if (e.target.tagName === 'A') {
|
|
|
sessionStorage.setItem('sidebar-scroll', sidebarScrollbox.scrollTop);
|
|
|
}
|
|
|
}, { passive: true });
|
|
|
var sidebarScrollTop = sessionStorage.getItem('sidebar-scroll');
|
|
|
sessionStorage.removeItem('sidebar-scroll');
|
|
|
if (sidebarScrollTop) {
|
|
|
// preserve sidebar scroll position when navigating via links within sidebar
|
|
|
sidebarScrollbox.scrollTop = sidebarScrollTop;
|
|
|
} else {
|
|
|
// scroll sidebar to current active section when navigating via "next/previous chapter" buttons
|
|
|
var activeSection = document.querySelector('#sidebar .active');
|
|
|
if (activeSection) {
|
|
|
activeSection.scrollIntoView({ block: 'center' });
|
|
|
}
|
|
|
}
|
|
|
</script>
|
|
|
|
|
|
<div id="page-wrapper" class="page-wrapper">
|
|
|
|
|
|
<div class="page">
|
|
|
<div id="menu-bar-hover-placeholder"></div>
|
|
|
<div id="menu-bar" class="menu-bar sticky">
|
|
|
<div class="left-buttons">
|
|
|
<label id="sidebar-toggle" class="icon-button" for="sidebar-toggle-anchor" title="Toggle Table of Contents" aria-label="Toggle Table of Contents" aria-controls="sidebar">
|
|
|
<i class="fa fa-bars"></i>
|
|
|
</label>
|
|
|
<button id="theme-toggle" class="icon-button" type="button" title="Change theme" aria-label="Change theme" aria-haspopup="true" aria-expanded="false" aria-controls="theme-list">
|
|
|
<i class="fa fa-paint-brush"></i>
|
|
|
</button>
|
|
|
<ul id="theme-list" class="theme-popup" aria-label="Themes" role="menu">
|
|
|
<li role="none"><button role="menuitem" class="theme" id="light">Light</button></li>
|
|
|
<li role="none"><button role="menuitem" class="theme" id="rust">Rust</button></li>
|
|
|
<li role="none"><button role="menuitem" class="theme" id="coal">Coal</button></li>
|
|
|
<li role="none"><button role="menuitem" class="theme" id="navy">Navy</button></li>
|
|
|
<li role="none"><button role="menuitem" class="theme" id="ayu">Ayu</button></li>
|
|
|
</ul>
|
|
|
<button id="search-toggle" class="icon-button" type="button" title="Search. (Shortkey: s)" aria-label="Toggle Searchbar" aria-expanded="false" aria-keyshortcuts="S" aria-controls="searchbar">
|
|
|
<i class="fa fa-search"></i>
|
|
|
</button>
|
|
|
</div>
|
|
|
|
|
|
<h1 class="menu-title">Rust 程序设计语言 简体中文版</h1>
|
|
|
|
|
|
<div class="right-buttons">
|
|
|
<a href="print.html" title="Print this book" aria-label="Print this book">
|
|
|
<i id="print-button" class="fa fa-print"></i>
|
|
|
</a>
|
|
|
<a href="https://github.com/KaiserY/trpl-zh-cn/tree/main" title="Git repository" aria-label="Git repository">
|
|
|
<i id="git-repository-button" class="fa fa-github"></i>
|
|
|
</a>
|
|
|
<a href="https://github.com/KaiserY/trpl-zh-cn/edit/main/src/ch15-05-interior-mutability.md" title="Suggest an edit" aria-label="Suggest an edit">
|
|
|
<i id="git-edit-button" class="fa fa-edit"></i>
|
|
|
</a>
|
|
|
|
|
|
</div>
|
|
|
</div>
|
|
|
|
|
|
<div id="search-wrapper" class="hidden">
|
|
|
<form id="searchbar-outer" class="searchbar-outer">
|
|
|
<input type="search" id="searchbar" name="searchbar" placeholder="Search this book ..." aria-controls="searchresults-outer" aria-describedby="searchresults-header">
|
|
|
</form>
|
|
|
<div id="searchresults-outer" class="searchresults-outer hidden">
|
|
|
<div id="searchresults-header" class="searchresults-header"></div>
|
|
|
<ul id="searchresults">
|
|
|
</ul>
|
|
|
</div>
|
|
|
</div>
|
|
|
|
|
|
<!-- Apply ARIA attributes after the sidebar and the sidebar toggle button are added to the DOM -->
|
|
|
<script>
|
|
|
document.getElementById('sidebar-toggle').setAttribute('aria-expanded', sidebar === 'visible');
|
|
|
document.getElementById('sidebar').setAttribute('aria-hidden', sidebar !== 'visible');
|
|
|
Array.from(document.querySelectorAll('#sidebar a')).forEach(function(link) {
|
|
|
link.setAttribute('tabIndex', sidebar === 'visible' ? 0 : -1);
|
|
|
});
|
|
|
</script>
|
|
|
|
|
|
<div id="content" class="content">
|
|
|
<main>
|
|
|
<h2 id="refcellt-和内部可变性模式"><a class="header" href="#refcellt-和内部可变性模式"><code>RefCell<T></code> 和内部可变性模式</a></h2>
|
|
|
<blockquote>
|
|
|
<p><a href="https://github.com/rust-lang/book/blob/main/src/ch15-05-interior-mutability.md">ch15-05-interior-mutability.md</a>
|
|
|
<br>
|
|
|
commit 5a3a64d60b0dd786c35ca4daada7a4d20da33e5e</p>
|
|
|
</blockquote>
|
|
|
<p><strong>内部可变性</strong>（<em>Interior mutability</em>）是 Rust 中的一个设计模式，它允许你即使在有不可变引用时也可以改变数据，这通常是借用规则所不允许的。为了改变数据，该模式在数据结构中使用 <code>unsafe</code> 代码来模糊 Rust 通常的可变性和借用规则。不安全代码表明我们在手动检查这些规则而不是让编译器替我们检查。第二十章会更详细地介绍不安全代码。</p>
|
|
|
<p>当可以确保代码在运行时会遵守借用规则，即使编译器不能保证的情况，可以选择使用那些运用内部可变性模式的类型。所涉及的 <code>unsafe</code> 代码将被封装进安全的 API 中，而外部类型仍然是不可变的。</p>
|
|
|
<p>让我们通过遵循内部可变性模式的 <code>RefCell<T></code> 类型来开始探索。</p>
|
|
|
<h3 id="通过-refcellt-在运行时检查借用规则"><a class="header" href="#通过-refcellt-在运行时检查借用规则">通过 <code>RefCell<T></code> 在运行时检查借用规则</a></h3>
|
|
|
<p>不同于 <code>Rc<T></code>，<code>RefCell<T></code> 代表其数据的唯一的所有权。那么是什么让 <code>RefCell<T></code> 不同于像 <code>Box<T></code> 这样的类型呢？回忆一下第四章所学的借用规则：</p>
|
|
|
<ol>
|
|
|
<li>在任意给定时刻，只能拥有一个可变引用或任意数量的不可变引用 <strong>之一</strong>（而不是两者）。</li>
|
|
|
<li>引用必须总是有效的。</li>
|
|
|
</ol>
|
|
|
<p>对于引用和 <code>Box<T></code>，借用规则的不可变性作用于编译时。对于 <code>RefCell<T></code>，这些不可变性作用于 <strong>运行时</strong>。对于引用，如果违反这些规则，会得到一个编译错误。而对于 <code>RefCell<T></code>，如果违反这些规则程序会 panic 并退出。</p>
|
|
|
<p>在编译时检查借用规则的优势是这些错误将在开发过程的早期被捕获，同时对运行时没有性能影响，因为所有的分析都提前完成了。为此，在编译时检查借用规则是大部分情况的最佳选择，这也正是其为何是 Rust 的默认行为。</p>
|
|
|
<p>相反在运行时检查借用规则的好处则是允许出现特定内存安全的场景，而它们在编译时检查中是不允许的。静态分析，正如 Rust 编译器，是天生保守的。但代码的一些属性不可能通过分析代码发现：其中最著名的就是 <a href="https://zh.wikipedia.org/wiki/%E5%81%9C%E6%9C%BA%E9%97%AE%E9%A2%98">停机问题（Halting Problem）</a>，这超出了本书的范畴，不过如果你感兴趣的话这是一个值得研究的有趣主题。</p>
|
|
|
<p>因为一些分析是不可能的，如果 Rust 编译器不能通过所有权规则编译，它可能会拒绝一个正确的程序；从这种角度考虑它是保守的。如果 Rust 接受不正确的程序，那么用户也就不会相信 Rust 所做的保证了。然而，如果 Rust 拒绝正确的程序，虽然会给程序员带来不便，但不会带来灾难。<code>RefCell<T></code> 正是用于当你确信代码遵守借用规则，而编译器不能理解和确定的时候。</p>
|
|
|
<p>类似于 <code>Rc<T></code>，<code>RefCell<T></code> 只能用于单线程场景。如果尝试在多线程上下文中使用<code>RefCell<T></code>，会得到一个编译错误。第十六章会介绍如何在多线程程序中使用 <code>RefCell<T></code> 的功能。</p>
|
|
|
<p>如下为选择 <code>Box<T></code>，<code>Rc<T></code> 或 <code>RefCell<T></code> 的理由：</p>
|
|
|
<ul>
|
|
|
<li><code>Rc<T></code> 允许相同数据有多个所有者；<code>Box<T></code> 和 <code>RefCell<T></code> 有单一所有者。</li>
|
|
|
<li><code>Box<T></code> 允许在编译时执行不可变或可变借用检查；<code>Rc<T></code>仅允许在编译时执行不可变借用检查；<code>RefCell<T></code> 允许在运行时执行不可变或可变借用检查。</li>
|
|
|
<li>因为 <code>RefCell<T></code> 允许在运行时执行可变借用检查，所以我们可以在即便 <code>RefCell<T></code> 自身是不可变的情况下修改其内部的值。</li>
|
|
|
</ul>
|
|
|
<p>在不可变值内部改变值就是 <strong>内部可变性</strong> 模式。让我们看看何时内部可变性是有用的，并讨论这是如何成为可能的。</p>
|
|
|
<h3 id="内部可变性不可变值的可变借用"><a class="header" href="#内部可变性不可变值的可变借用">内部可变性：不可变值的可变借用</a></h3>
|
|
|
<p>借用规则的一个推论是当有一个不可变值时，不能可变地借用它。例如，如下代码不能编译：</p>
|
|
|
<pre><code class="language-rust ignore does_not_compile">fn main() {
|
|
|
let x = 5;
|
|
|
let y = &mut x;
|
|
|
}</code></pre>
|
|
|
<p>如果尝试编译，会得到如下错误：</p>
|
|
|
<pre><code class="language-console">$ cargo run
|
|
|
Compiling borrowing v0.1.0 (file:///projects/borrowing)
|
|
|
error[E0596]: cannot borrow `x` as mutable, as it is not declared as mutable
|
|
|
--> src/main.rs:3:13
|
|
|
|
|
|
|
3 | let y = &mut x;
|
|
|
| ^^^^^^ cannot borrow as mutable
|
|
|
|
|
|
|
help: consider changing this to be mutable
|
|
|
|
|
|
|
2 | let mut x = 5;
|
|
|
| +++
|
|
|
|
|
|
For more information about this error, try `rustc --explain E0596`.
|
|
|
error: could not compile `borrowing` (bin "borrowing") due to 1 previous error
|
|
|
</code></pre>
|
|
|
<p>然而，特定情况下，令一个值在其方法内部能够修改自身，而在其他代码中仍视为不可变，是很有用的。值方法外部的代码就不能修改其值了。<code>RefCell<T></code> 是一个获得内部可变性的方法。<code>RefCell<T></code> 并没有完全绕开借用规则，编译器中的借用检查器允许内部可变性并相应地在运行时检查借用规则。如果违反了这些规则，会出现 panic 而不是编译错误。</p>
|
|
|
<p>让我们通过一个实际的例子来探索何处可以使用 <code>RefCell<T></code> 来修改不可变值并看看为何这么做是有意义的。</p>
|
|
|
<h4 id="内部可变性的用例mock-对象"><a class="header" href="#内部可变性的用例mock-对象">内部可变性的用例：mock 对象</a></h4>
|
|
|
<p>有时在测试中程序员会用某个类型替换另一个类型，以便观察特定的行为并断言它是被正确实现的。这个占位符类型被称为 <strong>测试替身</strong>(<em>test double</em>)。就像电影制作中的替身演员 (<em>stunt double</em>) 一样，替代演员完成高难度的场景。测试替身在运行测试时替代某个类型。<strong>mock 对象</strong> 是特定类型的测试替身，它们记录测试过程中发生了什么以便可以断言操作是正确的。</p>
|
|
|
<p>虽然 Rust 中的对象与其他语言中的对象并不是一回事，Rust 也没有像其他语言那样在标准库中内建 mock 对象功能，不过我们确实可以创建一个与 mock 对象有着相同功能的结构体。</p>
|
|
|
<p>如下是一个我们想要测试的场景：我们在编写一个记录某个值与最大值的差距的库，并根据当前值与最大值的差距来发送消息。例如，这个库可以用于记录用户所允许的 API 调用数量限额。</p>
|
|
|
<p>该库只提供记录与最大值的差距，以及何种情况发送什么消息的功能。使用此库的程序则期望提供实际发送消息的机制：程序可以选择记录一条消息、发送 email、发送短信等等。库本身无需知道这些细节；只需实现其提供的 <code>Messenger</code> trait 即可。示例 15-20 展示了库代码：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust noplayground">pub trait Messenger {
|
|
|
fn send(&self, msg: &str);
|
|
|
}
|
|
|
|
|
|
pub struct LimitTracker<'a, T: Messenger> {
|
|
|
messenger: &'a T,
|
|
|
value: usize,
|
|
|
max: usize,
|
|
|
}
|
|
|
|
|
|
impl<'a, T> LimitTracker<'a, T>
|
|
|
where
|
|
|
T: Messenger,
|
|
|
{
|
|
|
pub fn new(messenger: &'a T, max: usize) -> LimitTracker<'a, T> {
|
|
|
LimitTracker {
|
|
|
messenger,
|
|
|
value: 0,
|
|
|
max,
|
|
|
}
|
|
|
}
|
|
|
|
|
|
pub fn set_value(&mut self, value: usize) {
|
|
|
self.value = value;
|
|
|
|
|
|
let percentage_of_max = self.value as f64 / self.max as f64;
|
|
|
|
|
|
if percentage_of_max >= 1.0 {
|
|
|
self.messenger.send("Error: You are over your quota!");
|
|
|
} else if percentage_of_max >= 0.9 {
|
|
|
self.messenger
|
|
|
.send("Urgent warning: You've used up over 90% of your quota!");
|
|
|
} else if percentage_of_max >= 0.75 {
|
|
|
self.messenger
|
|
|
.send("Warning: You've used up over 75% of your quota!");
|
|
|
}
|
|
|
}
|
|
|
}</code></pre>
|
|
|
<p><span class="caption">示例 15-20：一个记录某个值与最大值差距的库，并根据此值的特定级别发出警告</span></p>
|
|
|
<p>这些代码中一个重要部分是拥有一个方法 <code>send</code> 的 <code>Messenger</code> trait，其获取一个 <code>self</code> 的不可变引用和文本信息。这个 trait 是 mock 对象所需要实现的接口库，这样 mock 就能像一个真正的对象那样使用了。另一个重要的部分是我们需要测试 <code>LimitTracker</code> 的 <code>set_value</code> 方法的行为。可以改变传递的 <code>value</code> 参数的值，不过 <code>set_value</code> 并没有返回任何可供断言的值。我们希望能够说，如果我们创建一个实现了 <code>Messenger</code> trait 和具有特定 <code>max</code> 值的 <code>LimitTracker</code> 时，当传递不同 <code>value</code> 值时，消息发送者应被告知发送合适的消息。</p>
|
|
|
<p>我们所需的 mock 对象是，调用 <code>send</code> 并不实际发送 email 或消息，而是只记录信息被通知要发送了。可以新建一个 mock 对象实例，用其创建 <code>LimitTracker</code>，调用 <code>LimitTracker</code> 的 <code>set_value</code> 方法，然后检查 mock 对象是否有我们期望的消息。示例 15-21 展示了一个如此尝试的 mock 对象实现，不过借用检查器并不允许：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust ignore does_not_compile"><span class="boring">pub trait Messenger {
|
|
|
</span><span class="boring"> fn send(&self, msg: &str);
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct LimitTracker<'a, T: Messenger> {
|
|
|
</span><span class="boring"> messenger: &'a T,
|
|
|
</span><span class="boring"> value: usize,
|
|
|
</span><span class="boring"> max: usize,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl<'a, T> LimitTracker<'a, T>
|
|
|
</span><span class="boring">where
|
|
|
</span><span class="boring"> T: Messenger,
|
|
|
</span><span class="boring">{
|
|
|
</span><span class="boring"> pub fn new(messenger: &'a T, max: usize) -> LimitTracker<'a, T> {
|
|
|
</span><span class="boring"> LimitTracker {
|
|
|
</span><span class="boring"> messenger,
|
|
|
</span><span class="boring"> value: 0,
|
|
|
</span><span class="boring"> max,
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> pub fn set_value(&mut self, value: usize) {
|
|
|
</span><span class="boring"> self.value = value;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let percentage_of_max = self.value as f64 / self.max as f64;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> if percentage_of_max >= 1.0 {
|
|
|
</span><span class="boring"> self.messenger.send("Error: You are over your quota!");
|
|
|
</span><span class="boring"> } else if percentage_of_max >= 0.9 {
|
|
|
</span><span class="boring"> self.messenger
|
|
|
</span><span class="boring"> .send("Urgent warning: You've used up over 90% of your quota!");
|
|
|
</span><span class="boring"> } else if percentage_of_max >= 0.75 {
|
|
|
</span><span class="boring"> self.messenger
|
|
|
</span><span class="boring"> .send("Warning: You've used up over 75% of your quota!");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>#[cfg(test)]
|
|
|
mod tests {
|
|
|
use super::*;
|
|
|
|
|
|
struct MockMessenger {
|
|
|
sent_messages: Vec<String>,
|
|
|
}
|
|
|
|
|
|
impl MockMessenger {
|
|
|
fn new() -> MockMessenger {
|
|
|
MockMessenger {
|
|
|
sent_messages: vec![],
|
|
|
}
|
|
|
}
|
|
|
}
|
|
|
|
|
|
impl Messenger for MockMessenger {
|
|
|
fn send(&self, message: &str) {
|
|
|
self.sent_messages.push(String::from(message));
|
|
|
}
|
|
|
}
|
|
|
|
|
|
#[test]
|
|
|
fn it_sends_an_over_75_percent_warning_message() {
|
|
|
let mock_messenger = MockMessenger::new();
|
|
|
let mut limit_tracker = LimitTracker::new(&mock_messenger, 100);
|
|
|
|
|
|
limit_tracker.set_value(80);
|
|
|
|
|
|
assert_eq!(mock_messenger.sent_messages.len(), 1);
|
|
|
}
|
|
|
}</code></pre>
|
|
|
<p><span class="caption">示例 15-21：尝试实现 <code>MockMessenger</code>，借用检查器不允许这么做</span></p>
|
|
|
<p>测试代码定义了一个 <code>MockMessenger</code> 结构体，其 <code>sent_messages</code> 字段为一个 <code>String</code> 值的 <code>Vec</code> 用来记录被告知发送的消息。我们还定义了一个关联函数 <code>new</code> 以便于新建从空消息列表开始的 <code>MockMessenger</code> 值。接着为 <code>MockMessenger</code> 实现 <code>Messenger</code> trait 这样就可以为 <code>LimitTracker</code> 提供一个 <code>MockMessenger</code>。在 <code>send</code> 方法的定义中，获取传入的消息作为参数并储存在 <code>MockMessenger</code> 的 <code>sent_messages</code> 列表中。</p>
|
|
|
<p>在测试中，我们测试了当 <code>LimitTracker</code> 被告知将 <code>value</code> 设置为超过 <code>max</code> 值 75% 的某个值。首先新建一个 <code>MockMessenger</code>，其从空消息列表开始。接着新建一个 <code>LimitTracker</code> 并传递新建 <code>MockMessenger</code> 的引用和 <code>max</code> 值 100。我们使用值 80 调用 <code>LimitTracker</code> 的 <code>set_value</code> 方法，这超过了 100 的 75%。接着断言 <code>MockMessenger</code> 中记录的消息列表应该有一条消息。</p>
|
|
|
<p>然而，这个测试是有问题的：</p>
|
|
|
<pre><code class="language-console">$ cargo test
|
|
|
Compiling limit-tracker v0.1.0 (file:///projects/limit-tracker)
|
|
|
error[E0596]: cannot borrow `self.sent_messages` as mutable, as it is behind a `&` reference
|
|
|
--> src/lib.rs:58:13
|
|
|
|
|
|
|
58 | self.sent_messages.push(String::from(message));
|
|
|
| ^^^^^^^^^^^^^^^^^^ `self` is a `&` reference, so the data it refers to cannot be borrowed as mutable
|
|
|
|
|
|
|
help: consider changing this to be a mutable reference in the `impl` method and the `trait` definition
|
|
|
|
|
|
|
2 ~ fn send(&mut self, msg: &str);
|
|
|
3 | }
|
|
|
...
|
|
|
56 | impl Messenger for MockMessenger {
|
|
|
57 ~ fn send(&mut self, message: &str) {
|
|
|
|
|
|
|
|
|
|
For more information about this error, try `rustc --explain E0596`.
|
|
|
error: could not compile `limit-tracker` (lib test) due to 1 previous error
|
|
|
</code></pre>
|
|
|
<p>不能修改 <code>MockMessenger</code> 来记录消息，因为 <code>send</code> 方法获取了 <code>self</code> 的不可变引用。我们也不能参考错误文本的建议使用 <code>&mut self</code> 替代，因为这样 <code>send</code> 的签名就不符合 <code>Messenger</code> trait 定义中的签名了（可以试着这么改，看看会出现什么错误信息）。</p>
|
|
|
<p>这正是内部可变性的用武之地！我们将通过 <code>RefCell</code> 来储存 <code>sent_messages</code>，然后 <code>send</code> 将能够修改 <code>sent_messages</code> 并储存消息。示例 15-22 展示了代码：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust noplayground"><span class="boring">pub trait Messenger {
|
|
|
</span><span class="boring"> fn send(&self, msg: &str);
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct LimitTracker<'a, T: Messenger> {
|
|
|
</span><span class="boring"> messenger: &'a T,
|
|
|
</span><span class="boring"> value: usize,
|
|
|
</span><span class="boring"> max: usize,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl<'a, T> LimitTracker<'a, T>
|
|
|
</span><span class="boring">where
|
|
|
</span><span class="boring"> T: Messenger,
|
|
|
</span><span class="boring">{
|
|
|
</span><span class="boring"> pub fn new(messenger: &'a T, max: usize) -> LimitTracker<'a, T> {
|
|
|
</span><span class="boring"> LimitTracker {
|
|
|
</span><span class="boring"> messenger,
|
|
|
</span><span class="boring"> value: 0,
|
|
|
</span><span class="boring"> max,
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> pub fn set_value(&mut self, value: usize) {
|
|
|
</span><span class="boring"> self.value = value;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let percentage_of_max = self.value as f64 / self.max as f64;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> if percentage_of_max >= 1.0 {
|
|
|
</span><span class="boring"> self.messenger.send("Error: You are over your quota!");
|
|
|
</span><span class="boring"> } else if percentage_of_max >= 0.9 {
|
|
|
</span><span class="boring"> self.messenger
|
|
|
</span><span class="boring"> .send("Urgent warning: You've used up over 90% of your quota!");
|
|
|
</span><span class="boring"> } else if percentage_of_max >= 0.75 {
|
|
|
</span><span class="boring"> self.messenger
|
|
|
</span><span class="boring"> .send("Warning: You've used up over 75% of your quota!");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>#[cfg(test)]
|
|
|
mod tests {
|
|
|
use super::*;
|
|
|
use std::cell::RefCell;
|
|
|
|
|
|
struct MockMessenger {
|
|
|
sent_messages: RefCell<Vec<String>>,
|
|
|
}
|
|
|
|
|
|
impl MockMessenger {
|
|
|
fn new() -> MockMessenger {
|
|
|
MockMessenger {
|
|
|
sent_messages: RefCell::new(vec![]),
|
|
|
}
|
|
|
}
|
|
|
}
|
|
|
|
|
|
impl Messenger for MockMessenger {
|
|
|
fn send(&self, message: &str) {
|
|
|
self.sent_messages.borrow_mut().push(String::from(message));
|
|
|
}
|
|
|
}
|
|
|
|
|
|
#[test]
|
|
|
fn it_sends_an_over_75_percent_warning_message() {
|
|
|
// --snip--
|
|
|
<span class="boring"> let mock_messenger = MockMessenger::new();
|
|
|
</span><span class="boring"> let mut limit_tracker = LimitTracker::new(&mock_messenger, 100);
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> limit_tracker.set_value(80);
|
|
|
</span>
|
|
|
assert_eq!(mock_messenger.sent_messages.borrow().len(), 1);
|
|
|
}
|
|
|
}</code></pre>
|
|
|
<p><span class="caption">示例 15-22：使用 <code>RefCell<T></code> 能够在外部值被认为是不可变的情况下修改内部值</span></p>
|
|
|
<p>现在 <code>sent_messages</code> 字段的类型是 <code>RefCell<Vec<String>></code> 而不是 <code>Vec<String></code>。在 <code>new</code> 函数中新建了一个 <code>RefCell<Vec<String>></code> 实例替代空 vector。</p>
|
|
|
<p>对于 <code>send</code> 方法的实现，第一个参数仍为 <code>self</code> 的不可变借用，这是符合方法定义的。我们调用 <code>self.sent_messages</code> 中 <code>RefCell</code> 的 <code>borrow_mut</code> 方法来获取 <code>RefCell</code> 中值的可变引用，这是一个 vector。接着可以对 vector 的可变引用调用 <code>push</code> 以便记录测试过程中看到的消息。</p>
|
|
|
<p>最后必须做出的修改位于断言中：为了看到其内部 vector 中有多少个项，需要调用 <code>RefCell</code> 的 <code>borrow</code> 以获取 vector 的不可变引用。</p>
|
|
|
<p>现在我们见识了如何使用 <code>RefCell<T></code>，让我们研究一下它怎样工作的！</p>
|
|
|
<h3 id="refcellt-在运行时记录借用"><a class="header" href="#refcellt-在运行时记录借用"><code>RefCell<T></code> 在运行时记录借用</a></h3>
|
|
|
<p>当创建不可变和可变引用时，我们分别使用 <code>&</code> 和 <code>&mut</code> 语法。对于 <code>RefCell<T></code> 来说，则是 <code>borrow</code> 和 <code>borrow_mut</code> 方法，这属于 <code>RefCell<T></code> 安全 API 的一部分。<code>borrow</code> 方法返回 <code>Ref<T></code> 类型的智能指针，<code>borrow_mut</code> 方法返回 <code>RefMut<T></code> 类型的智能指针。这两个类型都实现了 <code>Deref</code>，所以可以当作常规引用对待。</p>
|
|
|
<p><code>RefCell<T></code> 记录当前有多少个活动的 <code>Ref<T></code> 和 <code>RefMut<T></code> 智能指针。每次调用 <code>borrow</code>，<code>RefCell<T></code> 将活动的不可变借用计数加一。当 <code>Ref<T></code> 值离开作用域时，不可变借用计数减一。就像编译时借用规则一样，<code>RefCell<T></code> 在任何时候只允许有多个不可变借用或一个可变借用。</p>
|
|
|
<p>如果我们尝试违反这些规则，相比引用时的编译时错误，<code>RefCell<T></code> 的实现会在运行时出现 panic。示例 15-23 展示了对示例 15-22 中 <code>send</code> 实现的修改，这里我们故意尝试在相同作用域创建两个可变借用以便演示 <code>RefCell<T></code> 不允许我们在运行时这么做：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust ignore panics"><span class="boring">pub trait Messenger {
|
|
|
</span><span class="boring"> fn send(&self, msg: &str);
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct LimitTracker<'a, T: Messenger> {
|
|
|
</span><span class="boring"> messenger: &'a T,
|
|
|
</span><span class="boring"> value: usize,
|
|
|
</span><span class="boring"> max: usize,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl<'a, T> LimitTracker<'a, T>
|
|
|
</span><span class="boring">where
|
|
|
</span><span class="boring"> T: Messenger,
|
|
|
</span><span class="boring">{
|
|
|
</span><span class="boring"> pub fn new(messenger: &'a T, max: usize) -> LimitTracker<'a, T> {
|
|
|
</span><span class="boring"> LimitTracker {
|
|
|
</span><span class="boring"> messenger,
|
|
|
</span><span class="boring"> value: 0,
|
|
|
</span><span class="boring"> max,
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> pub fn set_value(&mut self, value: usize) {
|
|
|
</span><span class="boring"> self.value = value;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let percentage_of_max = self.value as f64 / self.max as f64;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> if percentage_of_max >= 1.0 {
|
|
|
</span><span class="boring"> self.messenger.send("Error: You are over your quota!");
|
|
|
</span><span class="boring"> } else if percentage_of_max >= 0.9 {
|
|
|
</span><span class="boring"> self.messenger
|
|
|
</span><span class="boring"> .send("Urgent warning: You've used up over 90% of your quota!");
|
|
|
</span><span class="boring"> } else if percentage_of_max >= 0.75 {
|
|
|
</span><span class="boring"> self.messenger
|
|
|
</span><span class="boring"> .send("Warning: You've used up over 75% of your quota!");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">#[cfg(test)]
|
|
|
</span><span class="boring">mod tests {
|
|
|
</span><span class="boring"> use super::*;
|
|
|
</span><span class="boring"> use std::cell::RefCell;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> struct MockMessenger {
|
|
|
</span><span class="boring"> sent_messages: RefCell<Vec<String>>,
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> impl MockMessenger {
|
|
|
</span><span class="boring"> fn new() -> MockMessenger {
|
|
|
</span><span class="boring"> MockMessenger {
|
|
|
</span><span class="boring"> sent_messages: RefCell::new(vec![]),
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span> impl Messenger for MockMessenger {
|
|
|
fn send(&self, message: &str) {
|
|
|
let mut one_borrow = self.sent_messages.borrow_mut();
|
|
|
let mut two_borrow = self.sent_messages.borrow_mut();
|
|
|
|
|
|
one_borrow.push(String::from(message));
|
|
|
two_borrow.push(String::from(message));
|
|
|
}
|
|
|
}
|
|
|
<span class="boring">
|
|
|
</span><span class="boring"> #[test]
|
|
|
</span><span class="boring"> fn it_sends_an_over_75_percent_warning_message() {
|
|
|
</span><span class="boring"> let mock_messenger = MockMessenger::new();
|
|
|
</span><span class="boring"> let mut limit_tracker = LimitTracker::new(&mock_messenger, 100);
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> limit_tracker.set_value(80);
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> assert_eq!(mock_messenger.sent_messages.borrow().len(), 1);
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}</span></code></pre>
|
|
|
<p><span class="caption">示例 15-23：在同一作用域中创建两个可变引用并观察 <code>RefCell<T></code> panic</span></p>
|
|
|
<p>这里为 <code>borrow_mut</code> 返回的 <code>RefMut</code> 智能指针创建了 <code>one_borrow</code> 变量。接着用相同的方式在变量 <code>two_borrow</code> 创建了另一个可变借用。这会在相同作用域中创建两个可变引用，这是不允许的。当运行库的测试时，示例 15-23 编译时不会有任何错误，不过测试会失败：</p>
|
|
|
<pre><code class="language-console">$ cargo test
|
|
|
Compiling limit-tracker v0.1.0 (file:///projects/limit-tracker)
|
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.91s
|
|
|
Running unittests src/lib.rs (target/debug/deps/limit_tracker-e599811fa246dbde)
|
|
|
|
|
|
running 1 test
|
|
|
test tests::it_sends_an_over_75_percent_warning_message ... FAILED
|
|
|
|
|
|
failures:
|
|
|
|
|
|
---- tests::it_sends_an_over_75_percent_warning_message stdout ----
|
|
|
thread 'tests::it_sends_an_over_75_percent_warning_message' panicked at src/lib.rs:60:53:
|
|
|
already borrowed: BorrowMutError
|
|
|
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
|
|
|
|
|
|
|
|
|
failures:
|
|
|
tests::it_sends_an_over_75_percent_warning_message
|
|
|
|
|
|
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
error: test failed, to rerun pass `--lib`
|
|
|
</code></pre>
|
|
|
<p>注意代码 panic 和信息 <code>already borrowed: BorrowMutError</code>。这也就是 <code>RefCell<T></code> 如何在运行时处理违反借用规则的情况。</p>
|
|
|
<p>像我们这里这样选择在运行时捕获借用错误而不是编译时意味着会发现在开发过程的后期才会发现的潜在错误，甚至有可能发布到生产环境才会发现。还会因为在运行时而不是编译时记录借用而导致少量的运行时性能惩罚。然而，使用 <code>RefCell</code> 使得在只允许不可变值的上下文中编写修改自身以记录消息的 mock 对象成为可能。虽然有取舍，但是我们可以选择使用 <code>RefCell<T></code> 来获得比常规引用所能提供的更多的功能。</p>
|
|
|
<h3 id="结合-rct-和-refcellt-来拥有多个可变数据所有者"><a class="header" href="#结合-rct-和-refcellt-来拥有多个可变数据所有者">结合 <code>Rc<T></code> 和 <code>RefCell<T></code> 来拥有多个可变数据所有者</a></h3>
|
|
|
<p><code>RefCell<T></code> 的一个常见用法是与 <code>Rc<T></code> 结合。回忆一下 <code>Rc<T></code> 允许对相同数据有多个所有者，不过只能提供数据的不可变访问。如果有一个储存了 <code>RefCell<T></code> 的 <code>Rc<T></code> 的话，就可以得到有多个所有者 <strong>并且</strong> 可以修改的值了！</p>
|
|
|
<p>例如，回忆示例 15-18 的 cons list 的例子中使用 <code>Rc<T></code> 使得多个列表共享另一个列表的所有权。因为 <code>Rc<T></code> 只存放不可变值，所以一旦创建了这些列表值后就不能修改。让我们加入 <code>RefCell<T></code> 来获得修改列表中值的能力。示例 15-24 展示了通过在 <code>Cons</code> 定义中使用 <code>RefCell<T></code>，我们就允许修改所有列表中的值了：</p>
|
|
|
<p><span class="filename">文件名：src/main.rs</span></p>
|
|
|
<pre><pre class="playground"><code class="language-rust edition2021">#[derive(Debug)]
|
|
|
enum List {
|
|
|
Cons(Rc<RefCell<i32>>, Rc<List>),
|
|
|
Nil,
|
|
|
}
|
|
|
|
|
|
use crate::List::{Cons, Nil};
|
|
|
use std::cell::RefCell;
|
|
|
use std::rc::Rc;
|
|
|
|
|
|
fn main() {
|
|
|
let value = Rc::new(RefCell::new(5));
|
|
|
|
|
|
let a = Rc::new(Cons(Rc::clone(&value), Rc::new(Nil)));
|
|
|
|
|
|
let b = Cons(Rc::new(RefCell::new(3)), Rc::clone(&a));
|
|
|
let c = Cons(Rc::new(RefCell::new(4)), Rc::clone(&a));
|
|
|
|
|
|
*value.borrow_mut() += 10;
|
|
|
|
|
|
println!("a after = {a:?}");
|
|
|
println!("b after = {b:?}");
|
|
|
println!("c after = {c:?}");
|
|
|
}</code></pre></pre>
|
|
|
<p><span class="caption">示例 15-24：使用 <code>Rc<RefCell<i32>></code> 创建可以修改的 <code>List</code></span></p>
|
|
|
<p>这里创建了一个 <code>Rc<RefCell<i32>></code> 实例并储存在变量 <code>value</code> 中以便之后直接访问。接着在 <code>a</code> 中用包含 <code>value</code> 的 <code>Cons</code> 成员创建了一个 <code>List</code>。需要克隆 <code>value</code> 以便 <code>a</code> 和 <code>value</code> 都能拥有其内部值 <code>5</code> 的所有权，而不是将所有权从 <code>value</code> 移动到 <code>a</code> 或者让 <code>a</code> 借用 <code>value</code>。</p>
|
|
|
<p>我们将列表 <code>a</code> 封装进了 <code>Rc<T></code> 这样当创建列表 <code>b</code> 和 <code>c</code> 时，它们都可以引用 <code>a</code>，正如示例 15-18 一样。</p>
|
|
|
<p>一旦创建了列表 <code>a</code>、<code>b</code> 和 <code>c</code>，我们将 <code>value</code> 的值加 10。为此对 <code>value</code> 调用了 <code>borrow_mut</code>，这里使用了第五章讨论的自动解引用功能（<a href="ch05-03-method-syntax.html#--%E8%BF%90%E7%AE%97%E7%AC%A6%E5%88%B0%E5%93%AA%E5%8E%BB%E4%BA%86">“<code>-></code> 运算符到哪去了？”</a> 部分）来解引用 <code>Rc<T></code> 以获取其内部的 <code>RefCell<T></code> 值。<code>borrow_mut</code> 方法返回 <code>RefMut<T></code> 智能指针，可以对其使用解引用运算符并修改其内部值。</p>
|
|
|
<p>当我们打印出 <code>a</code>、<code>b</code> 和 <code>c</code> 时，可以看到它们都拥有修改后的值 15 而不是 5：</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.63s
|
|
|
Running `target/debug/cons-list`
|
|
|
a after = Cons(RefCell { value: 15 }, Nil)
|
|
|
b after = Cons(RefCell { value: 3 }, Cons(RefCell { value: 15 }, Nil))
|
|
|
c after = Cons(RefCell { value: 4 }, Cons(RefCell { value: 15 }, Nil))
|
|
|
</code></pre>
|
|
|
<p>这是非常巧妙的！通过使用 <code>RefCell<T></code>，我们可以拥有一个表面上不可变的 <code>List</code>，不过可以使用 <code>RefCell<T></code> 中提供内部可变性的方法来在需要时修改数据。<code>RefCell<T></code> 的运行时借用规则检查也确实保护我们免于出现数据竞争——有时为了数据结构的灵活性而付出一些性能是值得的。注意 <code>RefCell<T></code> 不能用于多线程代码！<code>Mutex<T></code> 是一个线程安全版本的 <code>RefCell<T></code> ，我们会在第十六章讨论 <code>Mutex<T></code>。</p>
|
|
|
|
|
|
</main>
|
|
|
|
|
|
<nav class="nav-wrapper" aria-label="Page navigation">
|
|
|
<!-- Mobile navigation buttons -->
|
|
|
<a rel="prev" href="ch15-04-rc.html" class="mobile-nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
|
|
|
<i class="fa fa-angle-left"></i>
|
|
|
</a>
|
|
|
|
|
|
<a rel="next prefetch" href="ch15-06-reference-cycles.html" class="mobile-nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
|
|
|
<i class="fa fa-angle-right"></i>
|
|
|
</a>
|
|
|
|
|
|
<div style="clear: both"></div>
|
|
|
</nav>
|
|
|
</div>
|
|
|
</div>
|
|
|
|
|
|
<nav class="nav-wide-wrapper" aria-label="Page navigation">
|
|
|
<a rel="prev" href="ch15-04-rc.html" class="nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
|
|
|
<i class="fa fa-angle-left"></i>
|
|
|
</a>
|
|
|
|
|
|
<a rel="next prefetch" href="ch15-06-reference-cycles.html" class="nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
|
|
|
<i class="fa fa-angle-right"></i>
|
|
|
</a>
|
|
|
</nav>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<script>
|
|
|
window.playground_copyable = true;
|
|
|
</script>
|
|
|
|
|
|
|
|
|
<script src="elasticlunr.min.js"></script>
|
|
|
<script src="mark.min.js"></script>
|
|
|
<script src="searcher.js"></script>
|
|
|
|
|
|
<script src="clipboard.min.js"></script>
|
|
|
<script src="highlight.js"></script>
|
|
|
<script src="book.js"></script>
|
|
|
|
|
|
<!-- Custom JS scripts -->
|
|
|
<script src="ferris.js"></script>
|
|
|
|
|
|
|
|
|
</div>
|
|
|
</body>
|
|
|
</html>
|
