内容简介:Full set of changes can be found
New Features
- Provide initial support for debugging with MSVC toolchain in CLion 2020.2. You can track current progress and restrictions here
- Enable intelligent highlighting inside macro call bodies when new macro expansion engine is used
-
Add initial implementation of
Move Filerefactoring. The refactoring currently supports moving a single file without submodules.
- Now Rust plugin is dynamically loadable on 2020.2. It allows you to install the plugin without restarting the IDE
-
Add intentions to convert a method call to UFCS and vice versa (by @Kobzol )
-
Add quick fixes to remove unused variable / parameter (by @Kobzol )
-
Add the quick fix to convert an immutable reference to a mutable one (by @Kobzol )
-
Update icons for Rust items. Now they are more similar to C/C++ icons. Also, fix visibility modifiers for some items in structure view
Before After
-
Make
Introduce variablerefactoring available as an intention (by @Kobzol ) -
Add or improve detection of the new compiler errors:
- Now highlighting of lint inspection annotations is associated with corresponding lint levels defined by lint check attributes like
allow,warn, etc. (by @Stzx )
- Basic support for
forbidattribute. Now messages from a forbidden lint are highlighted as errors in the editor (by @Stzx )
- Allow a user to change mutability of parameters in
Extract Functiondialog (by @Kobzol )
- Report type errors for references with different mutability even if a type is not fully known (by @Kobzol )
- Enable
Convert match statement to if letintention for irrefutable patterns (by @Kobzol )
- Show unique editor tab names for
main.rs,lib.rsandCargo.toml(by @Kobzol )
- Improve text for
Convert to typequick fix (by @Kobzol )
- Update
Wrong type arguments numberinspection (by @Kobzol )
- Replace
Remove all type argumentsquick fix withRemove redundant type argumentsquick fix (by @Stzx )
Fixes
- Take into account namespaces when name shadowing occurs. For example, now
use anyhow::anyhowdoesn’t break name resolution
- Fix false positive about not allowed
impl Traitin associated type binding (by @Kobzol )
- Fix false positive for
Match must be exhaustiveerror (by @Mcat12 )
- Fix usage replacement in
Extract Enum Variantrefactoring (by @Kobzol )
- Support tuple struct fields in
Make publicquick fix (by @Kobzol )
- Make
Selfinside impl of enum to be resolved to both impl and enum items (by @fan-tom )
- Don’t trigger
Main function not foundinspection if the file has top-level errors (by @Kobzol )
- Fix
Go to Declarationfrom associated type bindings on 2020.2
- Fix parentheses completion for Fn* traits (by @Kobzol )
- Liveness analysis takes into account destructured struct fields (by @Kobzol )
- Fix
Join Linesaction for doc comment lines (by @Stzx )
- Disable
Promote Module to DirectoryandDowngrade Module to Filerefactorings for invalid files in the editor (by @Kobzol )
- Correctly handle symlinked Cargo projects (by @Jezza )
- Fix
#[macro_export(local_inner_macros)]when used with the experimental macro expansion engine
- Fix macro expansion infinite progress on 2020.2
- Properly render types in annotations on 2020.2
- Properly escape text in a test output pane
-
Get rid of options to disable the Test Tool window
-
Fix some exceptions:
- In
Remove referenceandChange return typequick fixes - When analysing file with an external linter
- During code folding of invalid macro calls
- On
Find Usagesin Macros 2.0 - In structure view and usage tooltip
- When formatting file with rustfmt on save
- In
Internal Improvements
- Enable proofreading in commit messages
- Provide issue / PR navigation in git log
Full set of changes can be found here
以上所述就是小编给大家介绍的《IntelliJ Rust Changelog #125》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
Release It!
Michael T. Nygard / Pragmatic Bookshelf / 2007-03-30 / USD 34.95
“Feature complete” is not the same as “production ready.” Whether it’s in Java, .NET, or Ruby on Rails, getting your application ready to ship is only half the battle. Did you design your system to......一起来看看 《Release It!》 这本书的介绍吧!