`RustFmt` error: "let chains are only allowed in Rust 2024 or later" but I'm on 2024
还没有人认领这个 Issue。
评估
调研方向
Start by reading the :RustFmt implementation and how it selects the Rust file’s edition; compare that behavior with cargo fmt on the workspace and crate-level edition configurations described in the report. Reproduce with a crate using let chains and edition 2024, then check whether the command works with an explicit crate edition. Done when :RustFmt formats the file without the Rust 2024 edition error.
由索引模型根据 Issue 内容生成。
描述
Project setup: I have a workspace that specifies the project versions, rust editions, and dependencies in the workspace Cargo.toml, and the crates contained within use:
version.workspace = true
edition.workspace = true
...
etc to refer to the configuration in the workspace Cargo.toml. I'm using edition "2024".
Vim setup: I'm on vim 8.2. rust.vim is already on its newest version. Here are the versions reported by :RustInfo.
rustfmt 1.8.0-stable (1159e78c47 2025-09-14)
rustc 1.90.0 (1159e78c4 2025-09-14)
cargo 1.90.0 (840b83a10 2025-07-30)
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 02 2025 12:39:01)
Included patches: 1-16, 647, 17-579, 1969, 580-647, 678, 648-1848, 4975, 5016, 5023, 5072, 2068, 1849-1854, 1857, 1855-1857, 1331, 1858, 1858-1859, 1873, 1860-1969, 1992, 1
970-1992, 2010, 1993-2068, 2106, 2069-2106, 2108, 2107-2109, 2109-3995, 4563, 4646, 4774, 4895, 4899, 4901, 4919, 213, 1840, 1846-1847, 2110-2112, 2121
Modified by [email protected]
Compiled by [email protected]
Issue: Running :RustFmt on a rust file that's using let chains fails with a location list of errors saying:
error: let chains are only allowed in Rust 2024 or later
The issue still reproduces this issue by using edition = "2024" on the crate instead of referring to the workspace edition. But cargo fmt on the command line works just fine. cargo fmt will produce the error above if I change to edition = "2018", for example. So rust.vim seems to not see the version correctly.
Any insights on what the underlying issue is and how to resolve it?
- 主要语言
- Vim Script
- 星标
- 4.2k
- 派生
- 323
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
rust-lang/rust.vim 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 76/100
-
It's Dead, Jim!未关闭
难度 5/5 一周以上 新手友好度 15/100
-
Remove hard coded edition fallback可能已有人在做 @alerque 于 230 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 35/100
-
难度 1/5 1 小时以内 新手友好度 55/100
-
难度 3/5 1-2 天 新手友好度 43/100
查看 rust-lang/rust.vim 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
bug documentation
难度 2/5 1-3 小时 新手友好度 83/100
cqframework/vscode-cql#198 ·
-
bug documentation good first issue help wanted testing
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
Show evidence time and supersede warnings in the memory inspector可能已有人在做 @Sinchanak-212 今天认领。 未关闭area: ux good first issue priority: medium
难度 2/5 1-3 小时 新手友好度 84/100
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
rohit746/pdf-view.nvim#109 ·
维护者通常 1 天内回复