From 4fd361343449bcdf7af4642851dc5dbf772f1a68 Mon Sep 17 00:00:00 2001 From: Pascal Hertleif Date: Mon, 11 Feb 2019 17:18:27 +0100 Subject: Fix some typos --- crates/ra_assists/src/lib.rs | 2 +- crates/ra_assists/src/remove_dbg.rs | 8 ++++---- crates/ra_db/src/cancellation.rs | 2 +- crates/ra_hir/src/code_model_api.rs | 6 +++--- crates/ra_hir/src/expr/scope.rs | 2 +- crates/ra_hir/src/ids.rs | 16 ++++++++-------- crates/ra_hir/src/nameres.rs | 2 +- crates/ra_hir/src/nameres/lower.rs | 2 +- crates/ra_hir/src/path.rs | 2 +- crates/ra_ide_api/src/completion.rs | 2 +- crates/ra_ide_api/src/completion/complete_fn_param.rs | 2 +- crates/ra_ide_api/src/goto_definition.rs | 8 ++++---- crates/ra_ide_api/src/hover.rs | 4 ++-- crates/ra_ide_api/src/impls.rs | 4 ++-- crates/ra_ide_api/src/lib.rs | 10 +++++----- crates/ra_ide_api/src/mock_analysis.rs | 2 +- crates/ra_ide_api/src/references.rs | 6 +++--- crates/ra_ide_api/src/symbol_index.rs | 12 ++++++------ crates/ra_mbe/src/lib.rs | 6 +++--- crates/ra_mbe/src/mbe_expander.rs | 2 +- crates/ra_project_model/src/cargo_workspace.rs | 2 +- crates/ra_vfs/src/io.rs | 4 ++-- crates/ra_vfs/src/lib.rs | 14 ++++++++------ crates/test_utils/src/lib.rs | 4 ++-- crates/test_utils/src/marks.rs | 8 +++++--- crates/thread_worker/src/lib.rs | 2 +- 26 files changed, 69 insertions(+), 65 deletions(-) (limited to 'crates') diff --git a/crates/ra_assists/src/lib.rs b/crates/ra_assists/src/lib.rs index c607a5142..7bd9b5ae6 100644 --- a/crates/ra_assists/src/lib.rs +++ b/crates/ra_assists/src/lib.rs @@ -1,4 +1,4 @@ -//! `ra_assits` crate provides a bunch of code assists, aslo known as code +//! `ra_assits` crate provides a bunch of code assists, also known as code //! actions (in LSP) or intentions (in IntelliJ). //! //! An assist is a micro-refactoring, which is automatically activated in diff --git a/crates/ra_assists/src/remove_dbg.rs b/crates/ra_assists/src/remove_dbg.rs index db260c6ca..2bed270a1 100644 --- a/crates/ra_assists/src/remove_dbg.rs +++ b/crates/ra_assists/src/remove_dbg.rs @@ -17,9 +17,9 @@ pub(crate) fn remove_dbg(mut ctx: AssistCtx) -> Option let macro_range = macro_call.syntax().range(); - // If the cursor is inside the macrocall, we'll try to maintain - // the cursor position by subtracting the length of dbg!( from the start - // of the filerange, otherwise we'll default to using the start of the macrocall + // If the cursor is inside the macro call, we'll try to maintain the cursor + // position by subtracting the length of dbg!( from the start of the file + // range, otherwise we'll default to using the start of the macro call let cursor_pos = { let file_range = ctx.frange.range; @@ -61,7 +61,7 @@ fn is_valid_macrocall(macro_call: &ast::MacroCall, macro_name: &str) -> Option Module { self.crate_root_impl(db) } @@ -351,7 +351,7 @@ impl Enum { db.type_for_def((*self).into()) } - // TODO move to a more general type + // TODO: move to a more general type /// Builds a resolver for type references inside this struct. pub fn resolver(&self, db: &impl HirDatabase) -> Resolver { // take the outer scope... @@ -495,7 +495,7 @@ impl Function { db.generic_params((*self).into()) } - // TODO move to a more general type for 'body-having' items + // TODO: move to a more general type for 'body-having' items /// Builds a resolver for code inside this item. pub fn resolver(&self, db: &impl HirDatabase) -> Resolver { // take the outer scope... diff --git a/crates/ra_hir/src/expr/scope.rs b/crates/ra_hir/src/expr/scope.rs index 44d5c2429..bb8d50db8 100644 --- a/crates/ra_hir/src/expr/scope.rs +++ b/crates/ra_hir/src/expr/scope.rs @@ -84,7 +84,7 @@ impl ExprScopes { fn add_bindings(&mut self, body: &Body, scope: ScopeId, pat: PatId) { match &body[pat] { Pat::Bind { name, .. } => { - // bind can have a subpattern, but it's actually not allowed + // bind can have a sub pattern, but it's actually not allowed // to bind to things in there let entry = ScopeEntry { name: name.clone(), pat }; self.scopes[scope].entries.push(entry) diff --git a/crates/ra_hir/src/ids.rs b/crates/ra_hir/src/ids.rs index d3fa7d266..8d81d5ebf 100644 --- a/crates/ra_hir/src/ids.rs +++ b/crates/ra_hir/src/ids.rs @@ -46,24 +46,24 @@ impl HirInterner { /// This module defines a bunch of ids we are using. The most important ones are /// probably `HirFileId` and `DefId`. -/// Input to the analyzer is a set of files, where each file is indentified by +/// Input to the analyzer is a set of files, where each file is identified by /// `FileId` and contains source code. However, another source of source code in /// Rust are macros: each macro can be thought of as producing a "temporary /// file". To assign an id to such a file, we use the id of the macro call that /// produced the file. So, a `HirFileId` is either a `FileId` (source code /// written by user), or a `MacroCallId` (source code produced by macro). /// -/// What is a `MacroCallId`? Simplifying, it's a `HirFileId` of a file containin -/// the call plus the offset of the macro call in the file. Note that this is a -/// recursive definition! However, the size_of of `HirFileId` is finite -/// (because everything bottoms out at the real `FileId`) and small +/// What is a `MacroCallId`? Simplifying, it's a `HirFileId` of a file +/// containing the call plus the offset of the macro call in the file. Note that +/// this is a recursive definition! However, the size_of of `HirFileId` is +/// finite (because everything bottoms out at the real `FileId`) and small /// (`MacroCallId` uses the location interner). #[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)] pub struct HirFileId(HirFileIdRepr); impl HirFileId { /// For macro-expansion files, returns the file original source file the - /// expansionoriginated from. + /// expansion originated from. pub fn original_file(self, db: &impl PersistentHirDatabase) -> FileId { match self.0 { HirFileIdRepr::File(file_id) => file_id, @@ -324,9 +324,9 @@ impl SourceFileItems { fn init(&mut self, source_file: &SourceFile) { // By walking the tree in bread-first order we make sure that parents - // get lower ids then children. That is, addding a new child does not + // get lower ids then children. That is, adding a new child does not // change parent's id. This means that, say, adding a new function to a - // trait does not chage ids of top-level items, which helps caching. + // trait does not change ids of top-level items, which helps caching. bfs(source_file.syntax(), |it| { if let Some(module_item) = ast::ModuleItem::cast(it) { self.alloc(module_item.syntax()); diff --git a/crates/ra_hir/src/nameres.rs b/crates/ra_hir/src/nameres.rs index 261ebdf97..ffb20d564 100644 --- a/crates/ra_hir/src/nameres.rs +++ b/crates/ra_hir/src/nameres.rs @@ -490,7 +490,7 @@ impl ItemMap { None => { // we still have path segments left, but the path so far // didn't resolve in the types namespace => no resolution - // (don't break here because curr_per_ns might contain + // (don't break here because `curr_per_ns` might contain // something in the value namespace, and it would be wrong // to return that) return (PerNs::none(), ReachedFixedPoint::No); diff --git a/crates/ra_hir/src/nameres/lower.rs b/crates/ra_hir/src/nameres/lower.rs index 7e9a3de2b..3cd496d7f 100644 --- a/crates/ra_hir/src/nameres/lower.rs +++ b/crates/ra_hir/src/nameres/lower.rs @@ -208,7 +208,7 @@ impl LoweredModule { } } ast::ModuleItemKind::Module(_) => { - // modules are handled separately direclty by nameres + // modules are handled separately directly by name res } }; } diff --git a/crates/ra_hir/src/path.rs b/crates/ra_hir/src/path.rs index 6a24c8aa7..8ed54607a 100644 --- a/crates/ra_hir/src/path.rs +++ b/crates/ra_hir/src/path.rs @@ -97,7 +97,7 @@ impl Path { return Some(q); } // TODO: this bottom up traversal is not too precise. - // Should we handle do a top-down analysiss, recording results? + // Should we handle do a top-down analysis, recording results? let use_tree_list = path.syntax().ancestors().find_map(ast::UseTreeList::cast)?; let use_tree = use_tree_list.parent_use_tree(); use_tree.path() diff --git a/crates/ra_ide_api/src/completion.rs b/crates/ra_ide_api/src/completion.rs index 83c243944..2b94931c6 100644 --- a/crates/ra_ide_api/src/completion.rs +++ b/crates/ra_ide_api/src/completion.rs @@ -30,7 +30,7 @@ pub use crate::completion::completion_item::{CompletionItem, CompletionItemKind, /// incomplete and can look really weird. /// /// Once the context is collected, we run a series of completion routines which -/// look at the context and produce completion items. One subtelty about this +/// look at the context and produce completion items. One subtlety about this /// phase is that completion engine should not filter by the substring which is /// already present, it should give all possible variants for the identifier at /// the caret. In other words, for diff --git a/crates/ra_ide_api/src/completion/complete_fn_param.rs b/crates/ra_ide_api/src/completion/complete_fn_param.rs index 43532226f..4d6416284 100644 --- a/crates/ra_ide_api/src/completion/complete_fn_param.rs +++ b/crates/ra_ide_api/src/completion/complete_fn_param.rs @@ -7,7 +7,7 @@ use rustc_hash::FxHashMap; use crate::completion::{CompletionContext, Completions, CompletionKind, CompletionItem}; -/// Complete repeated parametes, both name and type. For example, if all +/// Complete repeated parameters, both name and type. For example, if all /// functions in a file have a `spam: &mut Spam` parameter, a completion with /// `spam: &mut Spam` insert text/label and `spam` lookup string will be /// suggested. diff --git a/crates/ra_ide_api/src/goto_definition.rs b/crates/ra_ide_api/src/goto_definition.rs index 413720960..96ed8c8e9 100644 --- a/crates/ra_ide_api/src/goto_definition.rs +++ b/crates/ra_ide_api/src/goto_definition.rs @@ -93,10 +93,10 @@ pub(crate) fn reference_definition( return Exact(nav); } Some(Resolution::GenericParam(..)) => { - // TODO go to the generic param def + // TODO: go to the generic param def } Some(Resolution::SelfType(_impl_block)) => { - // TODO go to the implemented type + // TODO: go to the implemented type } None => {} } @@ -133,8 +133,8 @@ mod tests { use crate::mock_analysis::analysis_and_position; - fn check_goto(fixuture: &str, expected: &str) { - let (analysis, pos) = analysis_and_position(fixuture); + fn check_goto(fixture: &str, expected: &str) { + let (analysis, pos) = analysis_and_position(fixture); let mut navs = analysis.goto_definition(pos).unwrap().unwrap().info; assert_eq!(navs.len(), 1); diff --git a/crates/ra_ide_api/src/hover.rs b/crates/ra_ide_api/src/hover.rs index 60b81567c..0888ab6de 100644 --- a/crates/ra_ide_api/src/hover.rs +++ b/crates/ra_ide_api/src/hover.rs @@ -71,8 +71,8 @@ pub(crate) fn type_of(db: &RootDatabase, frange: FileRange) -> Option { } } -// FIXME: this should not really use navigation target. Rather, approximatelly -// resovled symbol should return a `DefId`. +// FIXME: this should not really use navigation target. Rather, approximately +// resolved symbol should return a `DefId`. fn doc_text_for(db: &RootDatabase, nav: NavigationTarget) -> Option { match (nav.description(db), nav.docs(db)) { (Some(desc), Some(docs)) => Some("```rust\n".to_string() + &*desc + "\n```\n\n" + &*docs), diff --git a/crates/ra_ide_api/src/impls.rs b/crates/ra_ide_api/src/impls.rs index 444c4aeb2..681bd808d 100644 --- a/crates/ra_ide_api/src/impls.rs +++ b/crates/ra_ide_api/src/impls.rs @@ -78,8 +78,8 @@ fn impls_for_trait( mod tests { use crate::mock_analysis::analysis_and_position; - fn check_goto(fixuture: &str, expected: &[&str]) { - let (analysis, pos) = analysis_and_position(fixuture); + fn check_goto(fixture: &str, expected: &[&str]) { + let (analysis, pos) = analysis_and_position(fixture); let navs = analysis.goto_implementation(pos).unwrap().unwrap().info; assert_eq!(navs.len(), expected.len()); diff --git a/crates/ra_ide_api/src/lib.rs b/crates/ra_ide_api/src/lib.rs index 2d090d9b4..de3ec4e0a 100644 --- a/crates/ra_ide_api/src/lib.rs +++ b/crates/ra_ide_api/src/lib.rs @@ -7,7 +7,7 @@ //! However, IDE specific bits of the analysis (most notably completion) happen //! in this crate. //! -//! The sibling `ra_ide_api_light` handles thouse bits of IDE functionality +//! The sibling `ra_ide_api_light` handles those bits of IDE functionality //! which are restricted to a single file and need only syntax. // For proving that RootDatabase is RefUnwindSafe. @@ -67,7 +67,7 @@ pub use ra_db::{ pub use hir::Documentation; // We use jemalloc mainly to get heap usage statistics, actual performance -// differnece is not measures. +// difference is not measures. #[cfg(feature = "jemalloc")] #[global_allocator] static ALLOC: jemallocator::Jemalloc = jemallocator::Jemalloc; @@ -221,12 +221,12 @@ impl Analysis { self.db.line_index(file_id) } - /// Selects the next syntactic nodes encopasing the range. + /// Selects the next syntactic nodes encompassing the range. pub fn extend_selection(&self, frange: FileRange) -> Cancelable { self.with_db(|db| extend_selection::extend_selection(db, frange)) } - /// Returns position of the mathcing brace (all types of braces are + /// Returns position of the matching brace (all types of braces are /// supported). pub fn matching_brace(&self, position: FilePosition) -> Option { let file = self.db.parse(position.file_id); @@ -316,7 +316,7 @@ impl Analysis { self.with_db(|db| references::find_all_refs(db, position)) } - /// Returns a short text descrbing element at position. + /// Returns a short text describing element at position. pub fn hover(&self, position: FilePosition) -> Cancelable>> { self.with_db(|db| hover::hover(db, position)) } diff --git a/crates/ra_ide_api/src/mock_analysis.rs b/crates/ra_ide_api/src/mock_analysis.rs index 8d8603062..017ac5de3 100644 --- a/crates/ra_ide_api/src/mock_analysis.rs +++ b/crates/ra_ide_api/src/mock_analysis.rs @@ -18,7 +18,7 @@ impl MockAnalysis { } /// Creates `MockAnalysis` using a fixture data in the following format: /// - /// ```notrust + /// ```rust,ignore /// //- /main.rs /// mod foo; /// fn main() {} diff --git a/crates/ra_ide_api/src/references.rs b/crates/ra_ide_api/src/references.rs index 2cb1cc9be..ca145f3e4 100644 --- a/crates/ra_ide_api/src/references.rs +++ b/crates/ra_ide_api/src/references.rs @@ -295,17 +295,17 @@ mod tests { fn test_rename(text: &str, new_name: &str, expected: &str) { let (analysis, position) = single_file_with_position(text); let source_change = analysis.rename(position, new_name).unwrap(); - let mut text_edit_bulder = ra_text_edit::TextEditBuilder::default(); + let mut text_edit_builder = ra_text_edit::TextEditBuilder::default(); let mut file_id: Option = None; if let Some(change) = source_change { for edit in change.source_file_edits { file_id = Some(edit.file_id); for atom in edit.edit.as_atoms() { - text_edit_bulder.replace(atom.delete, atom.insert.clone()); + text_edit_builder.replace(atom.delete, atom.insert.clone()); } } } - let result = text_edit_bulder.finish().apply(&*analysis.file_text(file_id.unwrap())); + let result = text_edit_builder.finish().apply(&*analysis.file_text(file_id.unwrap())); assert_eq_text!(expected, &*result); } } diff --git a/crates/ra_ide_api/src/symbol_index.rs b/crates/ra_ide_api/src/symbol_index.rs index de0f46134..15348124b 100644 --- a/crates/ra_ide_api/src/symbol_index.rs +++ b/crates/ra_ide_api/src/symbol_index.rs @@ -5,20 +5,20 @@ //! symbols. The backbone of the index is the **awesome** `fst` crate by //! @BurntSushi. //! -//! In a nutshell, you give a set of strings to the `fst`, and it builds a +//! In a nutshell, you give a set of strings to `fst`, and it builds a //! finite state machine describing this set of strings. The strings which //! could fuzzy-match a pattern can also be described by a finite state machine. -//! What is freakingly cool is that you can now traverse both state machines in +//! What is freaking cool is that you can now traverse both state machines in //! lock-step to enumerate the strings which are both in the input set and //! fuzz-match the query. Or, more formally, given two languages described by -//! fsts, one can build an product fst which describes the intersection of the +//! FSTs, one can build a product FST which describes the intersection of the //! languages. //! //! `fst` does not support cheap updating of the index, but it supports unioning -//! of state machines. So, to account for changing source code, we build an fst -//! for each library (which is assumed to never change) and an fst for each rust +//! of state machines. So, to account for changing source code, we build an FST +//! for each library (which is assumed to never change) and an FST for each Rust //! file in the current workspace, and run a query against the union of all -//! those fsts. +//! those FSTs. use std::{ cmp::Ordering, hash::{Hash, Hasher}, diff --git a/crates/ra_mbe/src/lib.rs b/crates/ra_mbe/src/lib.rs index ec2fd1eb5..cdca3cafb 100644 --- a/crates/ra_mbe/src/lib.rs +++ b/crates/ra_mbe/src/lib.rs @@ -109,7 +109,7 @@ mod tests { use super::*; - // Good first issue (although a slightly chellegning one): + // Good first issue (although a slightly challenging one): // // * Pick a random test from here // https://github.com/intellij-rust/intellij-rust/blob/c4e9feee4ad46e7953b1948c112533360b6087bb/src/test/kotlin/org/rust/lang/core/macros/RsMacroExpansionTest.kt @@ -171,8 +171,8 @@ impl_froms!(TokenTree: Leaf, Subtree); let (invocation_tt, _) = ast_to_token_tree(macro_invocation.token_tree().unwrap()).unwrap(); - let expaned = rules.expand(&invocation_tt).unwrap(); - assert_eq!(expaned.to_string(), expansion); + let expanded = rules.expand(&invocation_tt).unwrap(); + assert_eq!(expanded.to_string(), expansion); } #[test] diff --git a/crates/ra_mbe/src/mbe_expander.rs b/crates/ra_mbe/src/mbe_expander.rs index f6177f078..1acba86ea 100644 --- a/crates/ra_mbe/src/mbe_expander.rs +++ b/crates/ra_mbe/src/mbe_expander.rs @@ -58,7 +58,7 @@ fn expand_rule(rule: &crate::Rule, input: &tt::Subtree) -> Option { /// /// The other side of the puzzle is `expand_subtree`, where we use the bindings /// to substitute meta variables in the output template. When expanding, we -/// maintain a `nesteing` stack of indicies whihc tells us which occurence from +/// maintain a `nesting` stack of indices which tells us which occurrence from /// the `Bindings` we should take. We push to the stack when we enter a /// repetition. /// diff --git a/crates/ra_project_model/src/cargo_workspace.rs b/crates/ra_project_model/src/cargo_workspace.rs index 8adf463a6..5866be519 100644 --- a/crates/ra_project_model/src/cargo_workspace.rs +++ b/crates/ra_project_model/src/cargo_workspace.rs @@ -12,7 +12,7 @@ use crate::Result; /// /// Note that internally, rust analyzer uses a different structure: /// `CrateGraph`. `CrateGraph` is lower-level: it knows only about the crates, -/// while this knows about `Pacakges` & `Targets`: purely cargo-related +/// while this knows about `Packages` & `Targets`: purely cargo-related /// concepts. #[derive(Debug, Clone)] pub struct CargoWorkspace { diff --git a/crates/ra_vfs/src/io.rs b/crates/ra_vfs/src/io.rs index dc0b84d5a..3952b200b 100644 --- a/crates/ra_vfs/src/io.rs +++ b/crates/ra_vfs/src/io.rs @@ -169,7 +169,7 @@ fn convert_notify_event(event: DebouncedEvent, sender: &Sender<(PathBuf, ChangeK // ignore } DebouncedEvent::Rescan => { - // TODO rescan all roots + // TODO: rescan all roots } DebouncedEvent::Create(path) => { sender.send((path, ChangeKind::Create)).unwrap(); @@ -185,7 +185,7 @@ fn convert_notify_event(event: DebouncedEvent, sender: &Sender<(PathBuf, ChangeK sender.send((dst, ChangeKind::Create)).unwrap(); } DebouncedEvent::Error(err, path) => { - // TODO should we reload the file contents? + // TODO: should we reload the file contents? log::warn!("watcher error \"{}\", {:?}", err, path); } } diff --git a/crates/ra_vfs/src/lib.rs b/crates/ra_vfs/src/lib.rs index 5d98d905c..3dd05197e 100644 --- a/crates/ra_vfs/src/lib.rs +++ b/crates/ra_vfs/src/lib.rs @@ -7,8 +7,10 @@ //! //! It is also responsible for watching the disk for changes, and for merging //! editor state (modified, unsaved files) with disk state. -//! TODO: Some LSP clients support watching the disk, so this crate should -//! to support custom watcher events (related to https://github.com/rust-analyzer/rust-analyzer/issues/131) +//! +//! TODO: Some LSP clients support watching the disk, so this crate should to +//! support custom watcher events (related to +//! ) //! //! VFS is based on a concept of roots: a set of directories on the file system //! which are watched for changes. Typically, there will be a root for each @@ -212,12 +214,12 @@ impl Vfs { let mut cur_files = Vec::new(); // While we were scanning the root in the background, a file might have // been open in the editor, so we need to account for that. - let exising = self.root2files[root] + let existing = self.root2files[root] .iter() .map(|&file| (self.files[file].path.clone(), file)) .collect::>(); for (path, text) in files { - if let Some(&file) = exising.get(&path) { + if let Some(&file) = existing.get(&path) { let text = Arc::clone(&self.files[file].text); cur_files.push((file, path, text)); continue; @@ -322,7 +324,7 @@ impl Vfs { mem::replace(&mut self.pending_changes, Vec::new()) } - /// Sutdown the VFS and terminate the background watching thread. + /// Shutdown the VFS and terminate the background watching thread. pub fn shutdown(self) -> thread::Result<()> { self.worker.shutdown() } @@ -347,7 +349,7 @@ impl Vfs { } fn remove_file(&mut self, file: VfsFile) { - //FIXME: use arena with removal + // FIXME: use arena with removal self.files[file].text = Default::default(); self.files[file].path = Default::default(); let root = self.files[file].root; diff --git a/crates/test_utils/src/lib.rs b/crates/test_utils/src/lib.rs index 09fc2e659..4d83af00c 100644 --- a/crates/test_utils/src/lib.rs +++ b/crates/test_utils/src/lib.rs @@ -113,9 +113,9 @@ pub struct FixtureEntry { pub text: String, } -/// Parses text wich looks like this: +/// Parses text which looks like this: /// -/// ```notrust +/// ```rust,ignore /// //- some meta /// line 1 /// line 2 diff --git a/crates/test_utils/src/marks.rs b/crates/test_utils/src/marks.rs index d2a84643c..107432926 100644 --- a/crates/test_utils/src/marks.rs +++ b/crates/test_utils/src/marks.rs @@ -1,10 +1,10 @@ //! This module implements manually tracked test coverage, which useful for //! quickly finding a test responsible for testing a particular bit of code. //! -//! See https://matklad.github.io/2018/06/18/a-trick-for-test-maintenance.html +//! See //! for details, but the TL;DR is that you write your test as //! -//! ```no-run +//! ```rust,no_run //! #[test] //! fn test_foo() { //! covers!(test_foo); @@ -13,7 +13,9 @@ //! //! and in the code under test you write //! -//! ```no-run +//! ```rust,no_run +//! # use test_utils::tested_by; +//! # fn some_condition() -> bool { true } //! fn foo() { //! if some_condition() { //! tested_by!(test_foo); diff --git a/crates/thread_worker/src/lib.rs b/crates/thread_worker/src/lib.rs index ca0aad136..a522a0843 100644 --- a/crates/thread_worker/src/lib.rs +++ b/crates/thread_worker/src/lib.rs @@ -65,7 +65,7 @@ impl WorkerHandle { } } -/// Sets up worker channels in a deadlock-avoind way. +/// Sets up worker channels in a deadlock-avoiding way. /// If one sets both input and output buffers to a fixed size, /// a worker might get stuck. fn worker_chan(buf: usize) -> (Worker, Receiver, Sender) { -- cgit v1.2.3