Bump pest_derive from 2.7.0 to 2.7.3

[dependabot]

Bumps pest_derive from 2.7.0 to 2.7.3.

Release notes

Sourced from pest_derive's releases.

v2.7.3

What's Changed

• A new stack implementation that should be faster and less space-consuming by @​TheVeryDarkness in pest-parser/pest#905
• small cargo clippy fixes + dependency bumps by @​tomtau in pest-parser/pest#921

Full Changelog: pest-parser/pest@v2.7.2...v2.7.3

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.7", features = ["grammar-extras"] }

Restoration of the pest3 work effort

We started a new discussion thread to brainstorm ideas for pest3, both in terms of breaking grammar and API changes. You can check it out here: pest-parser/pest#885

v2.7.2

What's Changed

• Implement Display for Expr and OptimizedExpr by @​TheVeryDarkness in pest-parser/pest#896
• Update license field following SPDX 2.1 license expression standard by @​frisoft in pest-parser/pest#898
• Add feature gated Cow module paths by @​veeenu in pest-parser/pest#900
• propagate non_exhaustive attribute to the generated Rule enums by @​tomtau in pest-parser/pest#901
• docs: fix small typo in match_range by @​LeoDog896 in pest-parser/pest#906

New Contributors

• @​frisoft made their first contribution in pest-parser/pest#898
• @​veeenu made their first contribution in pest-parser/pest#900
• @​LeoDog896 made their first contribution in pest-parser/pest#906

Full Changelog: pest-parser/pest@v2.7.1...v2.7.2

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.7", features = ["grammar-extras"] }

Restoration of the pest3 work effort

We started a new discussion thread to brainstorm ideas for pest3, both in terms of breaking grammar and API changes. You can check it out here: pest-parser/pest#885

v2.7.1

What's Changed

... (truncated)

Commits

• ec61e92 small cargo clippy fixes + dependency bumps (#921)
• 734ba66 A new stack implementation that should be faster and less space-consuming (#905)
• fe53557 docs: fix small typo in match_range (#906)
• 5bfa99e propagate non_exhaustive attribute to the generated Rule enums (#901)
• da0feb0 Add feature gated Cow module paths (#900)
• 4d51b5b Update license field following SPDX 2.1 license expression standard (#898)
• 02cffe6 Implement Display for Expr and OptimizedExpr (#896)
• ac0aed3 Adding get_input() to types that already have public as_str() 🏷️ (#890)
• 48e0a8b Implement core::fmt::Display for OptimizedExpr (#889)
• 597e09b Merging Spans ♻️ (#887)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[hiddewie]

@dependabot merge