Bump pest_derive from 2.5.6 to 2.6.1

[dependabot]

Bumps pest_derive from 2.5.6 to 2.6.1.

Release notes

Sourced from pest_derive's releases.

v2.6.1: pest as a git dependency

What's Changed

• ci: fix for cargo-msrv needing at least 1.59 now by @​tomtau in pest-parser/pest#850
• Mitigate errors in reporting grammars that can cause the parser to run indefinetely by @​Tartasprint in pest-parser/pest#848
• Removed TODO about removed box syntax by @​Tartasprint in pest-parser/pest#854
• derive/examples: add a help menu grammar and parser by @​e-dant in pest-parser/pest#856
• feat: add simple Position/Span From implementations for LineColLocation by @​HoloTheDrunk in pest-parser/pest#860
• Swap precedence of negation and factorial by @​SandaruKasa in pest-parser/pest#865
• Conditional source-tree bootstrapping by @​tomtau and @​iptq in pest-parser/pest#866

New Contributors

• @​Tartasprint made their first contribution in pest-parser/pest#848
• @​e-dant made their first contribution in pest-parser/pest#856
• @​HoloTheDrunk made their first contribution in pest-parser/pest#860
• @​SandaruKasa made their first contribution in pest-parser/pest#865

Full Changelog: pest-parser/pest@v2.6.0...v2.6.1

Using pest as a git dependency

pest v2.6.1 contains a patch for the longstanding problem that pest couldn't be used as a git dependency due to the bootstrapping process. It should be possible now with a special feature flag as follows:

pest = { git = "https://github.com/.../pest.git", rev = "..." }
pest_derive = { git = "https://github.com/.../pest.git", rev = "...", features = ["not-bootstrap-in-src"]}

Note that the compilation time will be higher due to the cargo library dependency. If that becomes an issue, you can still use the old workarounds, e.g. cloning the repo, running cargo bootstrap there and specifying the dependency as a path to the locally cloned repo instead of git.

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 is a known issue and will be fixed in the future (e.g. by increasing MSRV and non_exhaustive annotations).

If you face a dependency problem where Cargo mixes different versions of pest due to transitive dependencies: pest-parser/pest#849 you can try adding the older pest to explicitly force it as follows:

pest = { version = "=2.5.6" }

v2.6.0: node tags

What's Changed

• Add basic support for node_tag, iterator, and meta grammar by @​tomtau in pest-parser/pest#832
• Fix #838 grammar error when only have //!, /// or //, allow writing empty pest grammar. by @​huacnlee in pest-parser/pest#839
• Implement ExactSizeIterator for Pair iterators by @​MucTepDayH16 in pest-parser/pest#833
• fuzz: decrease the call limit in the json fuzzer by @​tomtau in pest-parser/pest#841

New Contributors

• @​MucTepDayH16 made their first contribution in pest-parser/pest#833

Full Changelog: pest-parser/pest@v2.5.7...v2.6.0

Introducing node tags

pest v2.6.0's grammar includes a new (optional) feature for labelling parts of rules (based on this idea posted by @​oovm : pest-parser/pest#550 ), e.g.:

... (truncated)

Commits

• 867da2e Conditional source-tree bootstrapping (#866)
• 5ce7b43 Swap precedence of negation and factorial (#865)
• a4c93a7 feat: add simple Position/Span From implementations for LineColLocation (#860)
• 9176af2 derive/examples: add a help menu grammar and parser (#856)
• 23831ec Removed TODO about removed box syntax (#854)
• 7f8411a Mitigate errors in reporting grammars that can cause the parser to run indefi...
• 2a97516 ci: fix for cargo-msrv needing at least 1.59 now (#850)
• 6355eae fuzz: decrease the call limit in the json fuzzer (#841)
• 20f0842 Implement ExactSizeIterator for Pair iterators (#833)
• 5a05e69 Fix #838 grammar error when only have //!, /// or //. (#839)
• 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 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)

[dependabot]

Superseded by #78.