build(deps): bump syn from 1.0.109 to 2.0.79

[dependabot]

Bumps syn from 1.0.109 to 2.0.79.

Release notes

Sourced from syn's releases.

2.0.79

• Fix infinite loop on parsing chained ranges (#1741)
• Fix panic in parsing use items containing absolute paths (#1742)

2.0.78

• Fix infinite loop on chained comparison (#1739)

2.0.77

• Support parsing Expr::Tuple in non-"full" mode (#1727)

2.0.76

• Enforce that tail call become keyword is followed by an expression (#1725)

2.0.75

• Automatically fill in missing turbofish when printing ExprPath and other paths in expression position (#1722)

2.0.74

• Fix "temporary is dropped and runs the destructor for type `impl Iterator`" regression affecting certain use of Generics iterator methods (#1719)

2.0.73

• Support parsing unnamed C varargs within function pointer types (#1711)
• Improve synthesized error message on unexpected tokens at the end of the expected contents of a delimited group (#1713)
• Support parsing unstable tail call syntax (#1714, rust-lang/rust#112788)
• Add Fields::members iterator (#1716, thanks @​Fancyflame)

2.0.72

• Parse use<'a, T> precise capturing bounds (#1707, thanks @​compiler-errors)

2.0.71

• Do not require mutable borrow in Punctuated::get() (#1706, thanks @​lemunozm)

2.0.70

• Improve parenthesization of closures, jumps, ranges, chained comparisons, and let (#1694, #1695, #1698, #1699, #1700)

2.0.69

• Correctly parenthesize labeled loops inside a break value (#1692)
• Add Punctuated::get and get_mut (#1693)

2.0.68

• Improve panic location when parse_quote! parses invalid syntax (#1690, thanks @​stepancheg)
• More efficient peek implementation for Group and Lifetime (#1687)

2.0.67

• Produce more accurate error message locations for errors located at the end of a nested group (#1679, #1680)
• Support peeking LitCStr in ParseStream::peek (#1682)

2.0.66

• Allow braced structs when parsing ExprLet (#1671)

2.0.65

... (truncated)

Commits

• 732e6e3 Release 2.0.79
• af63396 Merge pull request #1742 from dtolnay/usecrateroot
• 31e8632 Fix construction of UseGroup containing crate roots
• 037861a Merge pull request #1741 from dtolnay/binoploop
• 8df4dd0 Force cursor to advance in parse_expr calls
• 09d020f Release 2.0.78
• 7eaebfb Merge pull request #1739 from dtolnay/chainedcomparison
• b3d2886 Fix infinite loop on chained comparison
• 3f3d0c5 Add regression test for issue 1738
• 346efae Touch up PR 1737
• 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)

[alexanderkjall]

I started to look at porting abscissa_derive to syn 2, as that would reduce the size of my dependency tree significantly, but it was non-trivial.

Do you have any plans on migrating to syn 2?