chore(deps): bump syn from 1.0.108 to 2.0.13

[dependabot]

Bumps syn from 1.0.108 to 2.0.13.

Release notes

Sourced from syn's releases.

2.0.13

• Improve spans of Expr::Field parsed from a float Literal (#1433, #1436)

2.0.12

• Refer to compile_error! by absolute path in token stream produced by syn::Error::to_compile_error (#1431, thanks @​smoelius)

2.0.11

• Improve error message on empty parens inside parse_nested_meta (#1428)

2.0.10

• Fix visibility being parsed incorrectly on macro invocations inside of a trait

2.0.9

• Disallow type items in an extern block, trait, or module from being marked default

2.0.8

• Treat try keyword as 2015-edition identifier in definition of try macro (#1422)

2.0.7

• Fix parsing of mut self inside of Type::BareFn

2.0.6

• Improve error message on missing ';' between statements (#1419)
• Keep non-brace macro invocations in trailing expr position as Expr::Macro (#1420)

2.0.5

• Expose ExprMacro data structure even when features="full" is not used (#1417)

2.0.4

• Improve error reporting when parsing identifiers and paths (#1415, #1416)

2.0.3

• Expose ExprGroup data structure even when features="full" is not used (#1412)

2.0.2

• Documentation improvements

2.0.1

• Add methods on syn::Meta for reporting error on an incorrect kind of attribute (#1409)

2.0.0

This release contains a batch of syntax tree improvements to incorporate ongoing Rust language development from the past 3.5 years since syn 1.

It never seems like an ideal time to finalize a syntax tree design, considering the frankly alarming number of syntax-disrupting language features currently in flight: keyword generics, restrictions, capabilities and contexts, conditional constness, new varieties of literals, dyn revamp such as explicitly dyn-safe traits and dyn-star, expression syntax in various phases of being added or being torn out (const blocks, try blocks, raw references), auto traits and negative impls, generalizations to higher rank trait bounds, async closures and static async trait methods, postfix keywords, pattern types, return type notation, unsafe attributes, …

The plan continues to be the same as laid out originally in the 1.0.0 release announcement:

Be aware that the underlying Rust language will continue to evolve. Syn is able to accommodate most kinds of Rust grammar changes via the nonexhaustive enums and Verbatim variants in the syntax tree, but we will plan to put out new major versions on a 12 to 24 month cadence to incorporate ongoing language changes as needed.

If anything, the takeaway from the 3.5 year longevity of syn 1 is that this period was tamer from a language development perspective than anticipated, but that is unlikely to last and I think around 24 months is still the correct cadence to expect between releases going forward.

... (truncated)

Commits

• ac5f15d Release 2.0.13
• 856c5dd Pull in proc-macro2 1.0.55's Literal span fixes
• 9aae2b4 Merge pull request #1436 from dtolnay/floatsubspan
• b0861b9 Ignore range_plus_one pedantic clippy lint
• 3b7c555 Improve spans of Expr::Field parsed from a float Literal
• b80c69a Link to issues tracking unimplemented syntax
• 80d4248 Improve stderr filtering to handle compiletest's "revisions" mechanism
• c001c26 Pass only .rs file paths to for_each_rust_file closure
• f7b4ef3 Share repo walkdir logic between the 2 repo walk tests
• ced12d4 Update "rust" repo benchmark to parse compiler and standard library only
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[bits-bot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[netlify]

✅ Deploy Preview for vector-project canceled.

Name	Link
🔨 Latest commit	45548c4
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/645b9eecf2eaa90007672e58

[netlify]

❌ Deploy Preview for vrl-playground failed.

Name	Link
🔨 Latest commit	45548c4
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/645b9eeca94d2a0008387c53

[neuronull]

The only reason we include syn was as a secondary dependency from using darling.

darling v0.14.3 contains changes to use syn internally as a re export, thus not requiring us to explicitly include it.

We are using the Meta and Lit structs from syn within maybe_float_or_int()

The latest version of darling is still using syn 1.0.x (pre the 2.0 breaking changes that affect us).

I think this PR when merged and included in a release, would unblock us from being able to use the latest of darling , and not depend on syn directly anymore:

TedDriggs/darling#226

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[spencergilbert]

This should be upgradeable now, but it was getting complicated and I was unsure of some of the changes, especially given my lack of experience in this libs. I dropped my work on spencer/update-syn-darling-serde_derive_internals

[dependabot]

Superseded by #17901.