Update Rust crate pest to v2.8.3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pest (source)	dependencies	minor	2.7.15 -> 2.8.3

---

Release Notes

pest-parser/pest (pest)

v2.8.3

Compare Source

What's Changed

• deps: drop thiserror for a manual impl by @​CosmicHorrorDev in #​1120
• feat: impl Error from core by @​CosmicHorrorDev in #​1121

Full Changelog: pest-parser/pest@v2.8.2...v2.8.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.8", features = ["grammar-extras"] }

v2.8.2

Compare Source

What's Changed

• Fix a broken link to Pair::as_span by @​jieyouxu in #​1112
• Upgrade install-action from v1 to v2 by @​tomtau in #​1114
• update to Unicode 17.0.0 by @​tomtau in #​1116

New Contributors

• @​jieyouxu made their first contribution in #​1112

Full Changelog: pest-parser/pest@v2.8.1...v2.8.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.8", features = ["grammar-extras"] }

v2.8.1

Compare Source

What's Changed

• Add reference to ws2markdown by @​dertuxmalwieder in #​1100
• remove once_cell (upon next MSRV bump!) by @​2ndDerivative in #​1102

The Minimum Supported Rust Version (MSRV) for default features is 1.80.0 now.

New Contributors

• @​dertuxmalwieder made their first contribution in #​1100
• @​2ndDerivative made their first contribution in #​1102

Full Changelog: pest-parser/pest@v2.8.0...v2.8.1

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.8", features = ["grammar-extras"] }

v2.8.0

Compare Source

What's Changed

• debugger: add long versions of the commands as well as all of their prefixes by @​alpaylan in #​1062
• Debugger: Fix deadlock on Windows by @​zaddach in #​1072
• Debugger: Fix command parsing on the debugger prompt by @​zaddach in #​1074
• Debugger: Allow specification of several breakpoints from cmdline args by @​zaddach in #​1075
• debugger: fixed cli-parsing of id command by @​Giftzwerg02 in #​1089
• rm some compiler warnings by @​yshavit in #​1093
• new rule: PUSH_LITERAL by @​yshavit in #​1092

A new rule PUSH_LITERAL(...).

PUSH_LITERAL("a"): This rule always matches and never consumes any input, and it pushes "a" to the stack. The argument must be a literal.

[!note]
You need to enable the "grammar-extras" feature as mentioned in the semantic versioning notes below in order to use this feature.

This new rule accomplishes the goals of #​880 (in a slightly different way). Instead of PUSH_OTHER("-", " "), this is just PUSH_LITERAL(" "). If you wanted to match A and then push B, you just combine them via a sequence: "-" ~ PUSH_LITERAL(" ").

This can be used to generalize quoted strings to a pair of matching but non-equal delimiters. For example, many programming languages let you express strings using either double or single quotes, and don't require escaping of the other:

string = ${ PUSH( "\"" | "'") ~ quoted_char* ~ POP }
quoted_char = @​{!PEEK ~ ANY } // simple version without escape sequences

// will parse "a'b" or 'a"b'

This happens to work because the starting and ending char are the same, but that's not always desirable. For example, we may want to allow strings to be delimited by either ( ... ) or < ... >, with similar rules as above, such that (a>) and <a)> are both valid.

With PUSH_LITERAL, this becomes:

string = ${ quote_open ~ quoted_char* ~ POP }
quote_open = @​{
  ( "(" ~ PUSH_LITERAL(")") )
| ( "<" ~ PUSH_LITERAL(">") )
}
quoted_char = @&#8203;{!PEEK ~ ANY } // simple version without escape sequences

New Contributors

• @​alpaylan made their first contribution in #​1062
• @​zaddach made their first contribution in #​1072
• @​Giftzwerg02 made their first contribution in #​1089
• @​yshavit made their first contribution in #​1093

Full Changelog: pest-parser/pest@v2.7.15...v2.8.0

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.8", features = ["grammar-extras"] }

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.