Releases: rust-lang/rust-analyzer
Releases · rust-lang/rust-analyzer
2022-07-18
Auto merge of #12785 - Logarithmus:feature/fix-negative-const-generic…
2022-07-11
Auto merge of #12732 - lnicola:bump-npm, r=lnicola Bump npm deps
2022-07-04
Auto merge of #12681 - lnicola:bump-deps, r=lnicola Bump deps
2022-06-27
Auto merge of #12638 - buffet:fix-typo, r=flodiebold Fix typo in build.rs
2022-06-20
Auto merge of #12581 - lnicola:changelog-number, r=lnicola internal: Handle fractional release numbers in changelog naming
2022-06-13
Auto merge of #12515 - Veykril:rustc-proc-macros, r=Veykril fix: Pass the build data to rustc_private crates With this all proc-macros should resolve in rustc now when setting up the build script running command properly.
2022-06-06
Auto merge of #12475 - Veykril:trait-impl-completion, r=Veykril fix: Fix trait impl completions using wrong insert position Fixes https://github.com/rust-lang/rust-analyzer/issues/12474
2022-05-30
Auto merge of #12409 - lowr:fix/usize-overflow, r=Veykril fix overflow during type inference for tuple struct patterns The following code causes integer overflow during type inference for (malformed) tuple struct patterns. ```rust struct S(usize); let S(.., a, b) = S(1); ``` It has been panicking only in debug builds, and working in a way in release builds but it was inconsistent with type inference for tuple patterns: ```rust struct S(usize); let S(.., a, b) = S(1); // a -> unknown, b -> usize let (.., a, b) = (1,); // a -> usize, b -> unknown ``` With this PR, the overflow no longer happens by utilizing `saturating_sub()` like in other places and type inference for tuple struct patterns is in line with that for tuple patterns.
2022-05-23
Auto merge of #12349 - lnicola:universal-vsix, r=lnicola internal: Publish universal VSIX to make VS happy
2022-05-17
Auto merge of #12292 - jonas-schievink:bump-extension-version, r=jona…