You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rust-analyzer version: rust-analyzer version: 0.3.1426-standalone (0a956ec 2023-03-05) rustc version: rustc 1.68.0 (2c8cc3432 2023-03-06) relevant settings: Check on save command is cargo clippy but error also occurs when configured with cargo check
The VS code extension for rust-analyzer reports that clone is missing on for a struct:
However, the struct derives Clone:
More importantly, running cargo build or cargo check from the command line doesn't give any error. I'm not sure what's causing the error but it did randomly show up recently. I'm assuming it was caused by an updated.
The only workaround I've found is replacing struct.clone with Clone::clone(&struct):
To reproduce:
git clone https://github.com/cucapra/filament.git
cd filament && code .
Happy to run more debugging commands to help figure out what's causing the problem.
The text was updated successfully, but these errors were encountered:
The warnings will be disabled by default in the next version, but it would be interesting to figure out what's happening here. The type there is barely a:
rust-analyzer version: rust-analyzer version: 0.3.1426-standalone (0a956ec 2023-03-05)
rustc version: rustc 1.68.0 (2c8cc3432 2023-03-06)
relevant settings: Check on save command is
cargo clippy
but error also occurs when configured withcargo check
The VS code extension for rust-analyzer reports that clone is missing on for a struct:
However, the struct derives Clone:
More importantly, running
cargo build
orcargo check
from the command line doesn't give any error. I'm not sure what's causing the error but it did randomly show up recently. I'm assuming it was caused by an updated.The only workaround I've found is replacing
struct.clone
withClone::clone(&struct)
:To reproduce:
Happy to run more debugging commands to help figure out what's causing the problem.
The text was updated successfully, but these errors were encountered: