Released: Nov 27, 2025

Aggiornamenti in 2025.2.5

Correzioni

• Code Insight
  • False positive [E0432] Unresolved import if dependencies were re-exported.
  • False positive: Non-constant value used in a constant expression.
  • False positive: errors are shown in a crate where some Cargo required-features are disabled.
  • False positive: "unresolved reference" for precise capture of const generics.
  • False positive: "Path prefix not necessary" with an associated item.
• Code Insight. Attributes
  • Unrecognized representation: #[repr(Rust)].
• Code Insight. Borrow checker
  • Full range (..) in tuple consumed in loop.
  • Async block ending with if.
  • Destructuring assignment is moved into lambda.
• Code Insight. Resolve
  • Multi-resolve for generic trait bound and explicit impl.
  • False positive: Unresolved import if redefined behind cfg.
• Completion
  • Inconsistent completion element tail text in the case of trait/impl method.
• Debugger
  • Evaluate Expression: extra tokens at EOF error for macro call.
  • Debugger: the value of self expression is not shown on hover.
• Highlighting
  • False Negative Unused import highlighting for std::hash::Hash.
  • False Negative Unused import highlighting for ExtractComponent trait from bevy crate.
• IDE
  • Detting idea.max.intellisense.filesize doesn't work in RustRover.
• Macros
  • Exception when expanding cfg! macro.
  • False Positive E0308: Error with bitflags! macro.
• Parser
  • "safe" and "unsafe" not supported in "extern "C"" blocks.
• Procedural macro
  • False-Positive: cannot find value in this scope for attribute-generated item in kameo crate.
• Run Configuration
  • Using the --release flag in the command box blocks this configuration from running.
• TOML
  • Crates.io new "security" category not recognized.
  • Crate not found: renamed package in workspace.dependencies.
  • Unused Crate in a package with cyclic dependencies (via dev-dependencies).
• Type inference
  • False-positive RPIT with 2 bounds of the same trait and different type parameters.
  • False error when calling function on associated type with overlapping trait bounds.
  • Multiresolved method on dyn Trait impls with different auto traits.
• No subsystem
  • Missing lifetime for method return value.
  • Infer type of multi-resolved method as unknown.
  • Wrong type inference on GAT in impl type.
  • Type mismatch between impl and trait function types.
  • External trait for arbitrary types.
  • cfg-disabled method in a trait impl should not influence name resolution.
  • Unresolved method from blanket impl for a type projection.
  • Completion: Self type should not be substituted in lookup element text.