Log message:
rust-analyzer: updated to 0.0.2022.03.07

2022.03.07:

New Features

* support locals with multiple declaration sites
* parse destructuring assignments.

Fixes

* add another case to the syntax fixup code.
* preserve order of generic args.
* fix semantic highlighting breaking for lifetimes in macros.
* lower string literal values.
* show variadic args in hover function signature.
* add type variable table to InferenceTableSnapshot.
* fix macro-calls expanding to items in if/while conditions.
* recognize Self as a proper keyword.
* add abort to safe intrinsics list.

Internal Improvements

* build release binaries on Ubuntu 18.04.
* add currently failing test for 11242.
* slightly refactor TextEdit.
* refactor syntax_highlighting.
* bring back syntax highlighting in test data.
* re-arrange ide_db modules.
* automatically change text color in logo based on dark mode.

Log message:
rust-analyzer: update to 0.0.2022.02.28.

2022-02-28

refactorings and FIXME fixes in text edit

2022-02-22

internal: Remove `name` fields from `MacroCallKind'

Log message:
rust-analyzer: updated to 0.0.2022.02.14

0.0.2022.02.14

New Features
* fix up syntax errors in attribute macro inputs to make completion work more often
* render whether a function is async / const / unsafe in completion details

Fixes
* (first contribution) add missing experimental capabilities.
* (first contribution) use text range of a mod name after macro expansion when \ 
renaming a module.
* don’t change references to super when renaming a module.
* fix documentation of SsrParams.

Internal Improvements
* make ascend_call_token iterative instead of recursive.
* fix serialization of WorkspaceSymbolParams.

Log message:
rust-analyzer: Use pre-1.58.0 format strings.

Log message:
rust-analyzer: updated to 0.0.2022.02.07

2022-02-07

11416: Fix eslint language server not working r=Veykril a=jackos

Allows the language server for eslint to work inside VS Code.

Log message:
rust-analyzer: updated to 0.0.2022.01.31

2022-01-31

fix: Fix `cfg_attr` invalidating derive identifier IDE functionalities r=Veykril \ 
a=Veykril

Proper fix for https://github.com/rust-analyzer/rust-analyzer/issues/11298
bors r+

Log message:
rust-analyzer: update to 0.0.2022.01.24.

2022-01-24

11334: fix: don't panic in semantics due to `cfg_attr` disrupting
offsets

Reduces the panic in
https://github.com/rust-analyzer/rust-analyzer/issues/11298 to an
early return, that means we won't resolve these cases again for
now, but this is better than constantly panicking in highlighting
and hovering.

2022-01-17

11287: fix: rust-analyzer spamming overly error message when
workspace not being loaded

Fixes #10120

Log message:
rust-analyzer: update to 0.0.2022.01.10.

2022.01.10

11238: fix: shrink the span of errors from attribute macros and
derives r=jonas-schievink a=jonas-schievink

Some procedural macros tend to get very large invocations, for
example RTIC's, leading to issues like
https://github.com/rtic-rs/cortex-m-rtic/issues/582, where almost
the entire screen is underlined while editing incomplete code in
the macro.

This PR shrinks the spans of errors from attribute macros and
derives to point only at the attribute, which also matches rustc
more closely.

Log message:
rust-analyzer: update to 0.0.2022.01.03.

2022.01.03

11177: internal: dont descend into comments r=Veykril a=jhgg

Log message:
rust-analyzer: update to 0.0.2021.12.27.

2021.12.27

11122: Remove note about alpha status from vscode extension
description

2021.12.20

11060: minor: Bump deps

2021.12.13

10995: internal: switch from trait-based TokenSource to simple
struct of arrays

cc #10765

The idea here is to try to simplify the interface as best as we
can. The original trait-based approach is a bit over-engineered
and hard to debug. Here, we replace callback with just data. The
next PR in series will replace the output `TreeSink` trait with
data as well.

The biggest drawback here is that we now require to materialize
all parser's input up-front. This is a bad fit for macro by example:
when you parse `$e:expr`, you might consume only part of the input.
However, today's trait-based solution doesn't really help -- we
were already materializing the whole thing! So, let's keep it
simple!