summaryrefslogtreecommitdiffstats
path: root/vendor/winnow/src/_topic/performance.rs
diff options
context:
space:
mode:
Diffstat (limited to 'vendor/winnow/src/_topic/performance.rs')
-rw-r--r--vendor/winnow/src/_topic/performance.rs10
1 files changed, 5 insertions, 5 deletions
diff --git a/vendor/winnow/src/_topic/performance.rs b/vendor/winnow/src/_topic/performance.rs
index fac12da4c..5bda958ee 100644
--- a/vendor/winnow/src/_topic/performance.rs
+++ b/vendor/winnow/src/_topic/performance.rs
@@ -6,7 +6,7 @@
//!
//! Tips
//! - When enough cases of an [`alt`] have unique prefixes, prefer [`dispatch`]
-//! - When parsing text, try to parse is as bytes (`u8`) rather than `char`s ([`BStr`] can make
+//! - When parsing text, try to parse as bytes (`u8`) rather than `char`s ([`BStr`] can make
//! debugging easier)
//! - Find simplified subsets of the grammar to parse, falling back to the full grammar when it
//! doesn't work. For example, when parsing json strings, parse them without support for escapes,
@@ -14,7 +14,7 @@
//! - Watch for large return types. A surprising place these can show up is when chaining parsers
//! with a tuple.
//!
-//! ## Built-time Performance
+//! ## Build-time Performance
//!
//! Returning complex types as `impl Trait` can negatively impact build times. This can hit in
//! surprising cases like:
@@ -24,7 +24,7 @@
//! # where
//! # I: winnow::stream::Stream<Token=O>,
//! # I: winnow::stream::StreamIsPartial,
-//! # E: winnow::error::ParseError<I>,
+//! # E: winnow::error::ParserError<I>,
//! {
//! // ...some chained combinators...
//! # winnow::token::any
@@ -38,9 +38,9 @@
//! # where
//! # I: winnow::stream::Stream<Token=O>,
//! # I: winnow::stream::StreamIsPartial,
-//! # E: winnow::error::ParseError<I>,
+//! # E: winnow::error::ParserError<I>,
//! {
-//! move |input: I| {
+//! move |input: &mut I| {
//! // ...some chained combinators...
//! # winnow::token::any
//! .parse_next(input)