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.
Breaking changes
Minimum required Rust version is raised from rustc 1.31 to 1.56.
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)
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/LGUG2Z/komorebi/pull/389
**Author:** [@dependabot[bot]](https://github.com/apps/dependabot)
**Created:** 4/3/2023
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `dependabot/cargo/syn-2.0.10`
---
### 📝 Commits (1)
- [`880538d`](https://github.com/LGUG2Z/komorebi/commit/880538d65d545aec3c5dc11e76c9344d880b942b) chore(deps): bump syn from 1.0.109 to 2.0.10
### 📊 Changes
**2 files changed** (+2 additions, -2 deletions)
<details>
<summary>View changed files</summary>
📝 `Cargo.lock` (+1 -1)
📝 `derive-ahk/Cargo.toml` (+1 -1)
</details>
### 📄 Description
Bumps [syn](https://github.com/dtolnay/syn) from 1.0.109 to 2.0.10.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/dtolnay/syn/releases">syn's releases</a>.</em></p>
<blockquote>
<h2>2.0.10</h2>
<ul>
<li>Fix visibility being parsed incorrectly on macro invocations inside of a trait</li>
</ul>
<h2>2.0.9</h2>
<ul>
<li>Disallow <code>type</code> items in an extern block, trait, or module from being marked <code>default</code></li>
</ul>
<h2>2.0.8</h2>
<ul>
<li>Treat <code>try</code> keyword as 2015-edition identifier in definition of try macro (<a href="https://redirect.github.com/dtolnay/syn/issues/1422">#1422</a>)</li>
</ul>
<h2>2.0.7</h2>
<ul>
<li>Fix parsing of <code>mut self</code> inside of Type::BareFn</li>
</ul>
<h2>2.0.6</h2>
<ul>
<li>Improve error message on missing ';' between statements (<a href="https://redirect.github.com/dtolnay/syn/issues/1419">#1419</a>)</li>
<li>Keep non-brace macro invocations in trailing expr position as Expr::Macro (<a href="https://redirect.github.com/dtolnay/syn/issues/1420">#1420</a>)</li>
</ul>
<h2>2.0.5</h2>
<ul>
<li>Expose <code>ExprMacro</code> data structure even when <code>features="full"</code> is not used (<a href="https://redirect.github.com/dtolnay/syn/issues/1417">#1417</a>)</li>
</ul>
<h2>2.0.4</h2>
<ul>
<li>Improve error reporting when parsing identifiers and paths (<a href="https://redirect.github.com/dtolnay/syn/issues/1415">#1415</a>, <a href="https://redirect.github.com/dtolnay/syn/issues/1416">#1416</a>)</li>
</ul>
<h2>2.0.3</h2>
<ul>
<li>Expose <code>ExprGroup</code> data structure even when <code>features="full"</code> is not used (<a href="https://redirect.github.com/dtolnay/syn/issues/1412">#1412</a>)</li>
</ul>
<h2>2.0.2</h2>
<ul>
<li>Documentation improvements</li>
</ul>
<h2>2.0.1</h2>
<ul>
<li>Add methods on syn::Meta for reporting error on an incorrect kind of attribute (<a href="https://redirect.github.com/dtolnay/syn/issues/1409">#1409</a>)</li>
</ul>
<h2>2.0.0</h2>
<p>This release contains a batch of syntax tree improvements to incorporate ongoing Rust language development from the past 3.5 years since syn 1.</p>
<p>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, …</p>
<p>The plan continues to be the same as laid out originally in the 1.0.0 release announcement:</p>
<blockquote>
<p>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 <code>Verbatim</code> 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.</p>
</blockquote>
<p>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.</p>
<!-- raw HTML omitted -->
<!-- raw HTML omitted -->
<h1>Breaking changes</h1>
<ul>
<li>Minimum required Rust version is raised from rustc 1.31 to 1.56.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/dtolnay/syn/commit/c4976f19f0ec56a878ae9203ac19e1be4b2c2326"><code>c4976f1</code></a> Release 2.0.10</li>
<li><a href="https://github.com/dtolnay/syn/commit/1f705d8ec66f4f1ec6d084b02d599eb8ba9dab93"><code>1f705d8</code></a> Remove precedence logic for the removed type ascription expression</li>
<li><a href="https://github.com/dtolnay/syn/commit/64ed2b1b190f9dc9e4ed06c0e9e41328e2e25cc8"><code>64ed2b1</code></a> Disallow visibility and defaultness on macro call in trait item position</li>
<li><a href="https://github.com/dtolnay/syn/commit/a33ffa388a19c3bdecd83cd7bc402124d310d356"><code>a33ffa3</code></a> Fix parsing of const, async, unsafe, and extern fns inside impl block</li>
<li><a href="https://github.com/dtolnay/syn/commit/94439aae5fe52ea9d753cef7e33262122e4022b5"><code>94439aa</code></a> Restore lookahead peek for better error message</li>
<li><a href="https://github.com/dtolnay/syn/commit/275d368069774115a70e1095098fdf3499f4a60f"><code>275d368</code></a> Release 2.0.9</li>
<li><a href="https://github.com/dtolnay/syn/commit/280d5e478dbe81b44f0e92f53168350bd508fdf7"><code>280d5e4</code></a> Remove dead code from ImplItemFn's ToTokens</li>
<li><a href="https://github.com/dtolnay/syn/commit/5036fd9c6e9b89809f93a6ffa17ac6663652baed"><code>5036fd9</code></a> Clean up ImplItemFn hack using ImplItem::Verbatim</li>
<li><a href="https://github.com/dtolnay/syn/commit/0f99d27656d31f8e87e70ccd0262d17ce2e580c5"><code>0f99d27</code></a> Factor out some common code for type parsing</li>
<li><a href="https://github.com/dtolnay/syn/commit/fd8d37ee5c942ea8f3067be72cc7386d999693f3"><code>fd8d37e</code></a> Disallow some nonsensical configurations of items</li>
<li>Additional commits viewable in <a href="https://github.com/dtolnay/syn/compare/1.0.109...2.0.10">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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)
</details>
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/LGUG2Z/komorebi/pull/389
Author: @dependabot[bot]
Created: 4/3/2023
Status: ❌ Closed
Base:
master← Head:dependabot/cargo/syn-2.0.10📝 Commits (1)
880538dchore(deps): bump syn from 1.0.109 to 2.0.10📊 Changes
2 files changed (+2 additions, -2 deletions)
View changed files
📝
Cargo.lock(+1 -1)📝
derive-ahk/Cargo.toml(+1 -1)📄 Description
Bumps syn from 1.0.109 to 2.0.10.
Release notes
Sourced from syn's releases.
... (truncated)
Commits
c4976f1Release 2.0.101f705d8Remove precedence logic for the removed type ascription expression64ed2b1Disallow visibility and defaultness on macro call in trait item positiona33ffa3Fix parsing of const, async, unsafe, and extern fns inside impl block94439aaRestore lookahead peek for better error message275d368Release 2.0.9280d5e4Remove dead code from ImplItemFn's ToTokens5036fd9Clean up ImplItemFn hack using ImplItem::Verbatim0f99d27Factor out some common code for type parsingfd8d37eDisallow some nonsensical configurations of itemsDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.