|
|
<!DOCTYPE HTML>
|
|
|
<html lang="en" class="light sidebar-visible" dir="ltr">
|
|
|
<head>
|
|
|
<!-- Book generated using mdBook -->
|
|
|
<meta charset="UTF-8">
|
|
|
<title>采用测试驱动开发完善库的功能 - 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" id="highlight-css" href="highlight.css">
|
|
|
<link rel="stylesheet" id="tomorrow-night-css" href="tomorrow-night.css">
|
|
|
<link rel="stylesheet" id="ayu-highlight-css" 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">
|
|
|
|
|
|
|
|
|
<!-- Provide site root and default themes to javascript -->
|
|
|
<script>
|
|
|
const path_to_root = "";
|
|
|
const default_light_theme = "light";
|
|
|
const default_dark_theme = "navy";
|
|
|
</script>
|
|
|
<!-- Start loading toc.js asap -->
|
|
|
<script src="toc.js"></script>
|
|
|
</head>
|
|
|
<body>
|
|
|
<div id="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="sidebar-toggle-anchor" class="hidden">
|
|
|
|
|
|
<!-- Hide / unhide sidebar before it is displayed -->
|
|
|
<script>
|
|
|
let sidebar = null;
|
|
|
const 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';
|
|
|
html.classList.remove('sidebar-visible');
|
|
|
html.classList.add("sidebar-" + sidebar);
|
|
|
</script>
|
|
|
|
|
|
<nav id="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="sidebar-resize-handle" class="sidebar-resize-handle">
|
|
|
<div class="sidebar-resize-indicator"></div>
|
|
|
</div>
|
|
|
</nav>
|
|
|
|
|
|
<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="default_theme">Auto</button></li>
|
|
|
<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/ch12-04-testing-the-librarys-functionality.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="采用测试驱动开发完善库的功能"><a class="header" href="#采用测试驱动开发完善库的功能">采用测试驱动开发完善库的功能</a></h2>
|
|
|
<!-- https://github.com/rust-lang/book/blob/main/src/ch12-04-testing-the-librarys-functionality.md -->
|
|
|
<!-- commit 3a30e4c1fbe641afc066b3af9eb01dcdf5ed8b24 -->
|
|
|
<p>现在我们将逻辑提取到了 <em>src/lib.rs</em> 并将所有的参数解析和错误处理留在了 <em>src/main.rs</em> 中，为代码的核心功能编写测试将更加容易。我们可以直接使用多种参数调用函数并检查返回值而无需从命令行运行二进制文件了。</p>
|
|
|
<p>在这一部分，我们将遵循测试驱动开发（Test Driven Development, TDD）的模式来逐步增加 <code>minigrep</code> 的搜索逻辑。它遵循如下步骤：</p>
|
|
|
<ol>
|
|
|
<li>编写一个失败的测试，并运行它以确保它失败的原因是你所期望的。</li>
|
|
|
<li>编写或修改足够的代码来使新的测试通过。</li>
|
|
|
<li>重构刚刚增加或修改的代码，并确保测试仍然能通过。</li>
|
|
|
<li>从步骤 1 开始重复！</li>
|
|
|
</ol>
|
|
|
<p>虽然这只是众多编写软件的方法之一，不过 TDD 有助于驱动代码的设计。在编写能使测试通过的代码之前编写测试有助于在开发过程中保持高测试覆盖率。</p>
|
|
|
<p>我们将以测试驱动来实现实际在文件内容中搜索查询字符串并返回匹配行的示例功能。我们将在一个叫做 <code>search</code> 的函数中增加这些功能。</p>
|
|
|
<h3 id="编写失败测试"><a class="header" href="#编写失败测试">编写失败测试</a></h3>
|
|
|
<p>去掉 <em>src/lib.rs</em> 和 <em>src/main.rs</em> 中用于检查程序行为的 <code>println!</code> 语句，因为不再真正需要它们了。接着我们会像<a href="ch11-01-writing-tests.html#%E6%B5%8B%E8%AF%95%E5%87%BD%E6%95%B0%E5%89%96%E6%9E%90">第十一章</a>那样增加一个 <code>test</code> 模块和一个测试函数。测试函数指定了 <code>search</code> 函数期望拥有的行为：它会获取一个需要查询的字符串和用来查询的文本，并只会返回包含请求的文本行。示例 12-15 展示了这个测试，它还不能编译：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust ignore does_not_compile"><span class="boring">use std::error::Error;
|
|
|
</span><span class="boring">use std::fs;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct Config {
|
|
|
</span><span class="boring"> pub query: String,
|
|
|
</span><span class="boring"> pub file_path: String,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl Config {
|
|
|
</span><span class="boring"> pub fn build(args: &[String]) -> Result<Config, &'static str> {
|
|
|
</span><span class="boring"> if args.len() < 3 {
|
|
|
</span><span class="boring"> return Err("not enough arguments");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let query = args[1].clone();
|
|
|
</span><span class="boring"> let file_path = args[2].clone();
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(Config { query, file_path })
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub fn run(config: Config) -> Result<(), Box<dyn Error>> {
|
|
|
</span><span class="boring"> let contents = fs::read_to_string(config.file_path)?;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(())
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>#[cfg(test)]
|
|
|
mod tests {
|
|
|
use super::*;
|
|
|
|
|
|
#[test]
|
|
|
fn one_result() {
|
|
|
let query = "duct";
|
|
|
let contents = "\
|
|
|
Rust:
|
|
|
safe, fast, productive.
|
|
|
Pick three.";
|
|
|
|
|
|
assert_eq!(vec!["safe, fast, productive."], search(query, contents));
|
|
|
}
|
|
|
}</code></pre>
|
|
|
<p><span class="caption">示例 12-15：创建一个我们期望的 <code>search</code> 函数的失败测试</span></p>
|
|
|
<p>这里选择使用 <code>"duct"</code> 作为这个测试中需要搜索的字符串。用来搜索的文本有三行，其中只有一行包含 <code>"duct"</code>。（注意双引号之后的反斜杠，这告诉 Rust 不要在字符串字面值内容的开头加入换行符）我们断言 <code>search</code> 函数的返回值只包含期望的那一行。</p>
|
|
|
<p>我们还不能运行这个测试并看到它失败，因为它甚至都还不能编译：<code>search</code> 函数还不存在呢！根据 TDD 的原则，我们将增加足够的代码来使其能够编译：一个总是会返回空 vector 的 <code>search</code> 函数定义，如示例 12-16 所示。然后这个测试应该能够编译并因为空 vector 并不匹配一个包含一行 <code>"safe, fast, productive."</code> 的 vector 而失败。</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust noplayground"><span class="boring">use std::error::Error;
|
|
|
</span><span class="boring">use std::fs;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct Config {
|
|
|
</span><span class="boring"> pub query: String,
|
|
|
</span><span class="boring"> pub file_path: String,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl Config {
|
|
|
</span><span class="boring"> pub fn build(args: &[String]) -> Result<Config, &'static str> {
|
|
|
</span><span class="boring"> if args.len() < 3 {
|
|
|
</span><span class="boring"> return Err("not enough arguments");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let query = args[1].clone();
|
|
|
</span><span class="boring"> let file_path = args[2].clone();
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(Config { query, file_path })
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub fn run(config: Config) -> Result<(), Box<dyn Error>> {
|
|
|
</span><span class="boring"> let contents = fs::read_to_string(config.file_path)?;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(())
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>pub fn search<'a>(query: &str, contents: &'a str) -> Vec<&'a str> {
|
|
|
vec![]
|
|
|
}
|
|
|
<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">
|
|
|
</span><span class="boring"> #[test]
|
|
|
</span><span class="boring"> fn one_result() {
|
|
|
</span><span class="boring"> let query = "duct";
|
|
|
</span><span class="boring"> let contents = "\
|
|
|
</span><span class="boring">Rust:
|
|
|
</span><span class="boring">safe, fast, productive.
|
|
|
</span><span class="boring">Pick three.";
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> assert_eq!(vec!["safe, fast, productive."], search(query, contents));
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}</span></code></pre>
|
|
|
<p><span class="caption">示例 12-16：刚好足够使测试通过编译的 <code>search</code> 函数定义</span></p>
|
|
|
<p>注意需要在 <code>search</code> 的签名中定义一个显式生命周期 <code>'a</code> 并用于 <code>contents</code> 参数和返回值。回忆一下<a href="ch10-03-lifetime-syntax.html">第十章</a>中讲到生命周期参数指定哪个参数的生命周期与返回值的生命周期相关联。在这个例子中，我们表明返回的 vector 中应该包含引用参数 <code>contents</code>（而不是参数<code>query</code>）slice 的字符串 slice。</p>
|
|
|
<p>换句话说，我们告诉 Rust 函数 <code>search</code> 返回的数据将与 <code>search</code> 函数中的参数 <code>contents</code> 的数据存在的一样久。这是非常重要的！为了使这个引用有效那么<strong>被</strong> slice 引用的数据也需要保持有效；如果编译器认为我们是在创建 <code>query</code> 而不是 <code>contents</code> 的字符串 slice，那么安全检查将是不正确的。</p>
|
|
|
<p>如果我们忘记添加生命周期注解而尝试编译此函数，就会得到如下错误：</p>
|
|
|
<pre><code class="language-console">$ cargo build
|
|
|
Compiling minigrep v0.1.0 (file:///projects/minigrep)
|
|
|
error[E0106]: missing lifetime specifier
|
|
|
--> src/lib.rs:28:51
|
|
|
|
|
|
|
28 | pub fn search(query: &str, contents: &str) -> Vec<&str> {
|
|
|
| ---- ---- ^ expected named lifetime parameter
|
|
|
|
|
|
|
= help: this function's return type contains a borrowed value, but the signature does not say whether it is borrowed from `query` or `contents`
|
|
|
help: consider introducing a named lifetime parameter
|
|
|
|
|
|
|
28 | pub fn search<'a>(query: &'a str, contents: &'a str) -> Vec<&'a str> {
|
|
|
| ++++ ++ ++ ++
|
|
|
|
|
|
For more information about this error, try `rustc --explain E0106`.
|
|
|
error: could not compile `minigrep` (lib) due to 1 previous error
|
|
|
</code></pre>
|
|
|
<p>Rust 不可能知道我们需要的是哪一个参数，所以需要显式地告诉它。因为参数 <code>contents</code> 包含了所有的文本而且我们希望返回匹配的那部分文本，所以我们知道 <code>contents</code> 是应该要使用生命周期语法来与返回值相关联的参数。</p>
|
|
|
<p>其他语言中并不需要你在函数签名中将参数与返回值相关联。所以这么做可能仍然感觉有些陌生，随着时间的推移这将会变得越来越容易。你可能想要将这个例子与第十章中<a href="ch10-03-lifetime-syntax.html#%E7%94%9F%E5%91%BD%E5%91%A8%E6%9C%9F%E7%A1%AE%E4%BF%9D%E5%BC%95%E7%94%A8%E6%9C%89%E6%95%88">“生命周期确保引用有效”</a>部分做对比。</p>
|
|
|
<p>现在运行测试：</p>
|
|
|
<pre><code class="language-console">$ cargo test
|
|
|
Compiling minigrep v0.1.0 (file:///projects/minigrep)
|
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 0.97s
|
|
|
Running unittests src/lib.rs (target/debug/deps/minigrep-9cd200e5fac0fc94)
|
|
|
|
|
|
running 1 test
|
|
|
test tests::one_result ... FAILED
|
|
|
|
|
|
failures:
|
|
|
|
|
|
---- tests::one_result stdout ----
|
|
|
|
|
|
thread 'tests::one_result' panicked at src/lib.rs:44:9:
|
|
|
assertion `left == right` failed
|
|
|
left: ["safe, fast, productive."]
|
|
|
right: []
|
|
|
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
|
|
|
|
|
|
|
|
|
failures:
|
|
|
tests::one_result
|
|
|
|
|
|
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>很好，测试失败了，这正是我们所期望的。修改代码来让测试通过吧！</p>
|
|
|
<h3 id="编写使测试通过的代码"><a class="header" href="#编写使测试通过的代码">编写使测试通过的代码</a></h3>
|
|
|
<p>目前测试之所以会失败是因为我们总是返回一个空的 vector。为了修复并实现 <code>search</code>，我们的程序需要遵循如下步骤：</p>
|
|
|
<ol>
|
|
|
<li>遍历内容的每一行文本。</li>
|
|
|
<li>查看这一行是否包含要搜索的字符串。</li>
|
|
|
<li>如果有，将这一行加入列表返回值中。</li>
|
|
|
<li>如果没有，什么也不做。</li>
|
|
|
<li>返回匹配到的结果列表。</li>
|
|
|
</ol>
|
|
|
<p>让我们一步一步的来，从遍历每行开始。</p>
|
|
|
<h4 id="使用-lines-方法逐行遍历"><a class="header" href="#使用-lines-方法逐行遍历">使用 <code>lines</code> 方法逐行遍历</a></h4>
|
|
|
<p>Rust 有一个有助于一行一行遍历字符串的方法，出于方便它被命名为 <code>lines</code>，它如示例 12-17 这样工作。注意这还不能编译：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust ignore does_not_compile"><span class="boring">use std::error::Error;
|
|
|
</span><span class="boring">use std::fs;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct Config {
|
|
|
</span><span class="boring"> pub query: String,
|
|
|
</span><span class="boring"> pub file_path: String,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl Config {
|
|
|
</span><span class="boring"> pub fn build(args: &[String]) -> Result<Config, &'static str> {
|
|
|
</span><span class="boring"> if args.len() < 3 {
|
|
|
</span><span class="boring"> return Err("not enough arguments");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let query = args[1].clone();
|
|
|
</span><span class="boring"> let file_path = args[2].clone();
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(Config { query, file_path })
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub fn run(config: Config) -> Result<(), Box<dyn Error>> {
|
|
|
</span><span class="boring"> let contents = fs::read_to_string(config.file_path)?;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(())
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>pub fn search<'a>(query: &str, contents: &'a str) -> Vec<&'a str> {
|
|
|
for line in contents.lines() {
|
|
|
// do something with line
|
|
|
}
|
|
|
}
|
|
|
<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">
|
|
|
</span><span class="boring"> #[test]
|
|
|
</span><span class="boring"> fn one_result() {
|
|
|
</span><span class="boring"> let query = "duct";
|
|
|
</span><span class="boring"> let contents = "\
|
|
|
</span><span class="boring">Rust:
|
|
|
</span><span class="boring">safe, fast, productive.
|
|
|
</span><span class="boring">Pick three.";
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> assert_eq!(vec!["safe, fast, productive."], search(query, contents));
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}</span></code></pre>
|
|
|
<p><span class="caption">示例 12-17：遍历 <code>contents</code> 的每一行</span></p>
|
|
|
<p><code>lines</code> 方法返回一个迭代器。<a href="ch13-02-iterators.html">第十三章</a>会深入了解迭代器，不过我们已经在<a href="ch03-05-control-flow.html#%E4%BD%BF%E7%94%A8-for-%E9%81%8D%E5%8E%86%E9%9B%86%E5%90%88">示例 3-5</a> 中见过使用迭代器的方法了，在那里使用了一个 <code>for</code> 循环和迭代器在一个集合的每一项上运行了一些代码。</p>
|
|
|
<h4 id="用查询字符串搜索每一行"><a class="header" href="#用查询字符串搜索每一行">用查询字符串搜索每一行</a></h4>
|
|
|
<p>接下来将会增加检查当前行是否包含查询字符串的功能。幸运的是，字符串类型为此也有一个叫做 <code>contains</code> 的实用方法！如示例 12-18 所示在 <code>search</code> 函数中加入 <code>contains</code> 方法调用。注意这仍然不能编译：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust ignore does_not_compile"><span class="boring">use std::error::Error;
|
|
|
</span><span class="boring">use std::fs;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct Config {
|
|
|
</span><span class="boring"> pub query: String,
|
|
|
</span><span class="boring"> pub file_path: String,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl Config {
|
|
|
</span><span class="boring"> pub fn build(args: &[String]) -> Result<Config, &'static str> {
|
|
|
</span><span class="boring"> if args.len() < 3 {
|
|
|
</span><span class="boring"> return Err("not enough arguments");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let query = args[1].clone();
|
|
|
</span><span class="boring"> let file_path = args[2].clone();
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(Config { query, file_path })
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub fn run(config: Config) -> Result<(), Box<dyn Error>> {
|
|
|
</span><span class="boring"> let contents = fs::read_to_string(config.file_path)?;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(())
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>pub fn search<'a>(query: &str, contents: &'a str) -> Vec<&'a str> {
|
|
|
for line in contents.lines() {
|
|
|
if line.contains(query) {
|
|
|
// 对文本行进行操作
|
|
|
}
|
|
|
}
|
|
|
}
|
|
|
<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">
|
|
|
</span><span class="boring"> #[test]
|
|
|
</span><span class="boring"> fn one_result() {
|
|
|
</span><span class="boring"> let query = "duct";
|
|
|
</span><span class="boring"> let contents = "\
|
|
|
</span><span class="boring">Rust:
|
|
|
</span><span class="boring">safe, fast, productive.
|
|
|
</span><span class="boring">Pick three.";
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> assert_eq!(vec!["safe, fast, productive."], search(query, contents));
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}</span></code></pre>
|
|
|
<p><span class="caption">示例 12-18：增加检查文本行是否包含 <code>query</code> 中字符串的功能</span></p>
|
|
|
<p>目前，我们正在构建功能。为了让代码能够编译，需要从函数体返回一个我们在函数签名中所声明的值。</p>
|
|
|
<h4 id="存储匹配的行"><a class="header" href="#存储匹配的行">存储匹配的行</a></h4>
|
|
|
<p>为了完成这个函数，我们需要一种方法来存储要返回的匹配行。为此可以在 <code>for</code> 循环之前创建一个可变的 vector 并调用 <code>push</code> 方法在 vector 中存放一个 <code>line</code>。在 <code>for</code> 循环之后，返回这个 vector，如示例 12-19 所示：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust ignore"><span class="boring">use std::error::Error;
|
|
|
</span><span class="boring">use std::fs;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct Config {
|
|
|
</span><span class="boring"> pub query: String,
|
|
|
</span><span class="boring"> pub file_path: String,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl Config {
|
|
|
</span><span class="boring"> pub fn build(args: &[String]) -> Result<Config, &'static str> {
|
|
|
</span><span class="boring"> if args.len() < 3 {
|
|
|
</span><span class="boring"> return Err("not enough arguments");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let query = args[1].clone();
|
|
|
</span><span class="boring"> let file_path = args[2].clone();
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(Config { query, file_path })
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub fn run(config: Config) -> Result<(), Box<dyn Error>> {
|
|
|
</span><span class="boring"> let contents = fs::read_to_string(config.file_path)?;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(())
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>pub fn search<'a>(query: &str, contents: &'a str) -> Vec<&'a str> {
|
|
|
let mut results = Vec::new();
|
|
|
|
|
|
for line in contents.lines() {
|
|
|
if line.contains(query) {
|
|
|
results.push(line);
|
|
|
}
|
|
|
}
|
|
|
|
|
|
results
|
|
|
}
|
|
|
<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">
|
|
|
</span><span class="boring"> #[test]
|
|
|
</span><span class="boring"> fn one_result() {
|
|
|
</span><span class="boring"> let query = "duct";
|
|
|
</span><span class="boring"> let contents = "\
|
|
|
</span><span class="boring">Rust:
|
|
|
</span><span class="boring">safe, fast, productive.
|
|
|
</span><span class="boring">Pick three.";
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> assert_eq!(vec!["safe, fast, productive."], search(query, contents));
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}</span></code></pre>
|
|
|
<p><span class="caption">示例 12-19：储存匹配的行以便可以返回它们</span></p>
|
|
|
<p>现在 <code>search</code> 函数应该返回只包含 <code>query</code> 的那些行，而测试应该会通过。让我们运行测试：</p>
|
|
|
<pre><code class="language-console">$ cargo test
|
|
|
Compiling minigrep v0.1.0 (file:///projects/minigrep)
|
|
|
Finished `test` profile [unoptimized + debuginfo] target(s) in 1.22s
|
|
|
Running unittests src/lib.rs (target/debug/deps/minigrep-9cd200e5fac0fc94)
|
|
|
|
|
|
running 1 test
|
|
|
test tests::one_result ... ok
|
|
|
|
|
|
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
Running unittests src/main.rs (target/debug/deps/minigrep-9cd200e5fac0fc94)
|
|
|
|
|
|
running 0 tests
|
|
|
|
|
|
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
Doc-tests minigrep
|
|
|
|
|
|
running 0 tests
|
|
|
|
|
|
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
|
|
|
|
|
|
</code></pre>
|
|
|
<p>测试通过了，我们知道它可以工作了！</p>
|
|
|
<p>现在正是可以考虑重构的时机，在保证测试通过，保持功能不变的前提下重构 <code>search</code> 函数。<code>search</code> 函数中的代码并不坏，不过并没有利用迭代器的一些实用功能。第十三章将回到这个例子并深入探索迭代器并看看如何改进代码。</p>
|
|
|
<h4 id="在-run-函数中使用-search-函数"><a class="header" href="#在-run-函数中使用-search-函数">在 <code>run</code> 函数中使用 <code>search</code> 函数</a></h4>
|
|
|
<p>现在 <code>search</code> 函数是可以工作并测试通过了的，我们需要实际在 <code>run</code> 函数中调用 <code>search</code>。需要将 <code>config.query</code> 值和 <code>run</code> 从文件中读取的 <code>contents</code> 传递给 <code>search</code> 函数。接着 <code>run</code> 会打印出 <code>search</code> 返回的每一行：</p>
|
|
|
<p><span class="filename">文件名：src/lib.rs</span></p>
|
|
|
<pre><code class="language-rust ignore"><span class="boring">use std::error::Error;
|
|
|
</span><span class="boring">use std::fs;
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">pub struct Config {
|
|
|
</span><span class="boring"> pub query: String,
|
|
|
</span><span class="boring"> pub file_path: String,
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring">impl Config {
|
|
|
</span><span class="boring"> pub fn build(args: &[String]) -> Result<Config, &'static str> {
|
|
|
</span><span class="boring"> if args.len() < 3 {
|
|
|
</span><span class="boring"> return Err("not enough arguments");
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> let query = args[1].clone();
|
|
|
</span><span class="boring"> let file_path = args[2].clone();
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> Ok(Config { query, file_path })
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}
|
|
|
</span><span class="boring">
|
|
|
</span>pub fn run(config: Config) -> Result<(), Box<dyn Error>> {
|
|
|
let contents = fs::read_to_string(config.file_path)?;
|
|
|
|
|
|
for line in search(&config.query, &contents) {
|
|
|
println!("{line}");
|
|
|
}
|
|
|
|
|
|
Ok(())
|
|
|
}
|
|
|
<span class="boring">
|
|
|
</span><span class="boring">pub fn search<'a>(query: &str, contents: &'a str) -> Vec<&'a str> {
|
|
|
</span><span class="boring"> let mut results = Vec::new();
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> for line in contents.lines() {
|
|
|
</span><span class="boring"> if line.contains(query) {
|
|
|
</span><span class="boring"> results.push(line);
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> results
|
|
|
</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">
|
|
|
</span><span class="boring"> #[test]
|
|
|
</span><span class="boring"> fn one_result() {
|
|
|
</span><span class="boring"> let query = "duct";
|
|
|
</span><span class="boring"> let contents = "\
|
|
|
</span><span class="boring">Rust:
|
|
|
</span><span class="boring">safe, fast, productive.
|
|
|
</span><span class="boring">Pick three.";
|
|
|
</span><span class="boring">
|
|
|
</span><span class="boring"> assert_eq!(vec!["safe, fast, productive."], search(query, contents));
|
|
|
</span><span class="boring"> }
|
|
|
</span><span class="boring">}</span></code></pre>
|
|
|
<p>这里仍然使用了 <code>for</code> 循环获取了 <code>search</code> 返回的每一行并打印出来。</p>
|
|
|
<p>现在整个程序应该可以工作了！让我们试一试，首先使用一个只会在艾米莉·狄金森的诗中返回一行的单词 “frog”：</p>
|
|
|
<pre><code class="language-console">$ cargo run -- frog poem.txt
|
|
|
Compiling minigrep v0.1.0 (file:///projects/minigrep)
|
|
|
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.38s
|
|
|
Running `target/debug/minigrep frog poem.txt`
|
|
|
How public, like a frog
|
|
|
</code></pre>
|
|
|
<p>不错！现在试试一个会匹配多行的单词，比如 “body”：</p>
|
|
|
<pre><code class="language-console">$ cargo run -- body poem.txt
|
|
|
Compiling minigrep v0.1.0 (file:///projects/minigrep)
|
|
|
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.0s
|
|
|
Running `target/debug/minigrep body poem.txt`
|
|
|
I'm nobody! Who are you?
|
|
|
Are you nobody, too?
|
|
|
How dreary to be somebody!
|
|
|
</code></pre>
|
|
|
<p>最后，让我们确保搜索一个在诗中哪里都没有的单词时不会得到任何行，比如 <em>monomorphization</em>：</p>
|
|
|
<pre><code class="language-console">$ cargo run -- monomorphization poem.txt
|
|
|
Compiling minigrep v0.1.0 (file:///projects/minigrep)
|
|
|
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.0s
|
|
|
Running `target/debug/minigrep monomorphization poem.txt`
|
|
|
</code></pre>
|
|
|
<p>非常好！我们创建了一个属于自己的迷你版经典工具，并学习了很多如何组织程序的知识。我们还学习了一些文件输入输出、生命周期、测试和命令行解析的内容。</p>
|
|
|
<p>为了使这个项目更丰满，我们将简要的展示如何处理环境变量和打印到标准错误，这两者在编写命令行程序时都很有用。</p>
|
|
|
|
|
|
</main>
|
|
|
|
|
|
<nav class="nav-wrapper" aria-label="Page navigation">
|
|
|
<!-- Mobile navigation buttons -->
|
|
|
<a rel="prev" href="ch12-03-improving-error-handling-and-modularity.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="ch12-05-working-with-environment-variables.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="ch12-03-improving-error-handling-and-modularity.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="ch12-05-working-with-environment-variables.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>
|
