An invalid self import was made ( E0431).The self import appears more than once in the list ( E0430).The self keyword cannot appear alone as the last segment in a use declaration ( E0429).The name for an item declaration conflicts with an external crate’s name ( E0260).The name chosen for an external crate conflicts with another external crate that has been imported into the current module ( E0259).An attempt was made to import an item whereas an extern crate with this name has already been imported ( E0254).IntelliJ Rust now detects more compiler errors: Type inference should now work faster thanks to changes in how common type inference cases are handled.The plugin now considers negative impl when inferring types.The recently added unstable Destruct trait is now derived for all types.Looping over a type parameter implementing the Iterator trait has been fixed and now works as expected.For instance, now the ? operator works for Poll. The unstable Try trait was moved to core::ops::try_trait::Try and its associated types were renamed. We’ve fixed the usage of the ? operator with the Try trait.We’ve fixed the inference of closure parameter types when closure is assigned to a variable and parameter types are inferred after the assignment.This fixes false-positive errors like type mismatch between Box and Box. We’ve implemented unsized coercions in the type inference engine.In this release cycle, we’ve implemented various fixes and improvements for type inference: As a result, when you type in macro calls, completion and highlighting should now work faster. ![]() We stopped doing some unnecessary cache invalidations. Note that Cargo settings have been moved to Preferences / Settings | Build, Execution, Deployment | Build Tools | Cargo for consistency with other settings for build tools. If you select the Any changes option, the project model will be updated automatically for all changes. For any changes made in the IDE, you’ll be offered the Load Cargo Changes button, which allows you to load changes manually. This means that the project model will be reloaded automatically only for external changes (for example, when you get updated files from version control). You can change the settings for project model reloading in Preferences / Settings | Build, Execution, Deployment | Build Tools.īy default, the Reload project after changes in the build scripts checkbox is ticked, and the External changes option is selected. Click on the button, and the IDE will load changes to make your project work correctly. IntelliJ Rust now also takes into account changes in Cargo config, the toolchain file and build scripts.Īfter you’ve changed configuration files, you will now see the floating Load Cargo Changes button. This change should make project model reloading more predictable. The plugin now detects changes in config files even if they are not saved to disk. In v2022.2, we’ve improved the way IntelliJ Rust updates the project model. There are plenty of other features and improvements – to learn about them all, read the detailed description below. The plugin can convert JSON to structs via copy-paste. IntelliJ Rust now highlights outdated or missing dependencies in Cargo.toml. We’ve improved performance and implemented various type inference improvements. In this release cycle, we’ve enabled a new approach for detecting changes in configuration files, as well as a new way to reload project models. Rename refactoring for metavariables in macros.Convert JSON to Rust types via copy-paste.Inspections for unused_must_use and clippy::double_must_use. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |