diff --git a/.github/workflows/rust-next.yml b/.github/workflows/rust-next.yml index 2e23b20..89e203f 100644 --- a/.github/workflows/rust-next.yml +++ b/.github/workflows/rust-next.yml @@ -56,7 +56,7 @@ jobs: components: rustfmt - uses: Swatinem/rust-cache@v2 - uses: taiki-e/install-action@cargo-hack - - name: Update dependencues + - name: Update dependencies run: cargo update - name: Build run: cargo test --workspace --no-run diff --git a/CHANGELOG.md b/CHANGELOG.md index 87f8e5a..dfebe04 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -75,7 +75,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/). - Don't correct `ang` ('angle' abbreviation) - Don't correct `dur` ('duration' abbreviation) -- Don't correct `lst` (used in place of 'list' when its a built-in) +- Don't correct `lst` (used in place of 'list' when it's a built-in) - Don't correct `GUID` acronym - Don't correct `IIS` acronym - Don't correct `IME` acronym @@ -601,7 +601,7 @@ Publish to PyPI (first attempt) ### Fixes -- Don't correct `nilable` as its used by the Ruby community +- Don't correct `nilable` as it's used by the Ruby community ## [1.13.3] - 2022-12-02 @@ -993,7 +993,7 @@ Note: MSRV is now 1.54 #### Performance - Due to new literal detection, finding identifiers is takes 10x longer. - Combined with word splitting, its only takes 3x longer. The majority of the + Combined with word splitting, it only takes 3x longer. The majority of the time is spent in dictionary lookups, so we don't expect this to have too much impact in the end. ## [1.0.10] - 2021-06-28 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 31cac6a..9ddfeb3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -7,13 +7,13 @@ appreciate any level you're willing to do. Need some new functionality to help? You can let us know by opening an [issue][new issue]. It's helpful to look through [all issues][all issues] in -case its already being talked about. +case it's already being talked about. ## Bug Reports Please let us know about what problems you run into, whether in behavior or ergonomics of API. You can do this by opening an [issue][new issue]. It's -helpful to look through [all issues][all issues] in case its already being +helpful to look through [all issues][all issues] in case it's already being talked about. ## Pull Requests diff --git a/crates/varcon-core/src/parser.rs b/crates/varcon-core/src/parser.rs index a3a0640..377e997 100644 --- a/crates/varcon-core/src/parser.rs +++ b/crates/varcon-core/src/parser.rs @@ -428,7 +428,7 @@ impl Type { let category = Category::parse_(input)?; let tag = winnow::combinator::opt(Tag::parse_).parse_next(input)?; let num = winnow::combinator::opt(winnow::ascii::digit1).parse_next(input)?; - let num = num.map(|s| s.parse().expect("parser ensured its a number")); + let num = num.map(|s| s.parse().expect("parser ensured it's a number")); let t = Type { category, tag, num }; Ok(t) })