Releases: rust-lang/rust-analyzer
Releases · rust-lang/rust-analyzer
2021-06-21
Merge #9346 9346: Refactor / clean up hir_ty tests r=flodiebold a=flodiebold Notable changes: - unify `check_types` and `check_mismatches` into `check`, which supports both kinds of annotations (`check_types` still exists because I didn't want to change all the annotations, but uses the same implementation) - because of that, `check_types` now fails on any type mismatches; also annotations always have to hit the exact range - there's also `check_no_mismatches` for when we explicitly just want to check that there are no type mismatches without giving any annotations (`check` will fail without annotations) - test annotations can now be overlapping (they point to the nearest line that has actual code in that range): ``` // ^^^^ annotation // ^^^^^^^^^ another annotation ``` Co-authored-by: Florian Diebold <flodiebold@gmail.com>
2021-06-14
Merge #9257 9257: internal: diagnostic code is mandatory r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
2021-06-07
Merge #9155 9155: internal: replace attribute with equivalent whitespace r=jonas-schievink a=jonas-schievink This is needed to that the `TokenMap` we create contains offsets that match the source. Currently the offsets don't match because the attribute is removed, shifting all subsequent token offsets by the attribute's text length. Currently this fix has no visible effect because we don't remap tokens in attribute macros. bors r+ Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
2021-05-31
Merge #9071 9071: minor: reenable incremental release builds r=jonas-schievink a=jonas-schievink forgot to turn this back on in https://github.com/rust-analyzer/rust-analyzer/pull/9069 Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
2021-05-24
Merge #8945 8945: fix: Make expected type work in more situations r=flodiebold a=flodiebold Also makes call info show the correct types for generic methods.   Co-authored-by: Florian Diebold <flodiebold@gmail.com>
2021-05-17
Merge #8845 8845: Generate the impl block via generate_trait_impl_text_from_impl r=Veykril a=hi-rustin Try to close https://github.com/rust-analyzer/rust-analyzer/issues/8827 Co-authored-by: hi-rustin <rustin.liu@gmail.com>
2021-05-10
Merge #8784
8784: feat: auto-insert `}` when typing `{` in use item r=jonas-schievink a=jonas-schievink
cc https://github.com/rust-analyzer/rust-analyzer/issues/8636
bors r+
Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
2021-05-03
Merge #8709 8709: cargo update r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <kjeremy@gmail.com>
2021-04-26
Merge #8658 8658: Check more carefully for cases where a rename can't be done r=Veykril a=dzhu Attempting to rename an element of a tuple field would previously replace the type with the new name, which doesn't make sense; now it fails instead. The check is done in both `prepare_rename` and `rename` so that the case is caught before the user is prompted for a new name. Some other existing failure cases are also now additionally checked in `prepare_rename`. Closes: #8592 (I threw in some doc edits for a relevant type; of course, I can remove those if the policy here is to be strict about scope of changes within a PR.) Co-authored-by: Danny Zhu <dzhu@dzhu.us>
2021-04-20
fix: no longer get stuck on windows reading both stdout & stderr is a common gotcha, you need to drain them concurrently to avoid deadlocks. Not sure why I didn't do the right thing from the start. Seems like I assumed the stderr is short? That's not the case when cargo spams `compiling xyz` messages