| Age | Commit message (Collapse) | Author | Lines |
|
|
|
fix: Fix flyimport not filtering via stability of import path
|
|
|
|
Only collect implicit visibile use symbols if they have renames
|
|
Otherwise this will pollute the index too much with unnecessary symbols
|
|
Make niches into nices
|
|
minor: Suggest better names when a type is a sequence
|
|
Split manual.adoc into markdown files, one for each chapter.
For the parts of the manual that are generated from source code doc
comments, update the comments to use markdown syntax and update the
code generators to write to `generated.md` files.
For the weekly release, stop copying the .adoc files to the
`rust-analyzer/rust-analyzer.github.io` at release time. Instead,
we'll sync the manual hourly from this repository.
See https://github.com/rust-analyzer/rust-analyzer.github.io/pull/226
for the sync. This PR should be merged first, and that PR needs to be
merged before the next weekly release.
This change is based on #15795, but rebased and updated. I've also
manually checked each page for markdown syntax issues and fixed any I
encountered.
Co-authored-by: Lukas Wirth <lukastw97@gmail.com>
Co-authored-by: Josh Rotenberg <joshrotenberg@gmail.com>
|
|
Previously, we'd suggest a type of `vec` for a value of type `Vec<T>`,
which is rarely what the user wants. We also had no suggestions for
values of type `&[T]`.
Instead, try to pluralise the inner type name, and fall back to
`items`.
|
|
|
|
internal: Record the use tree index in glob imports
|
|
Keep already computed inlay hint properties instead of late resolving them
|
|
|
|
|
|
|
|
feat: Implement `arbitrary-self-types`
|
|
|
|
fix: Fix flycheck panicking with "once" invocation strategy
|
|
feat: Provide a config to control auto-insertion of `await` and `iter()`
|
|
internal: Treat cfg fetching failures as a warning
|
|
fix: Fix `ItemScope` not recording glob imports
|
|
We only ever have one flycheck runner no matter the number of workspaces, so just kick off flycheck for it immediately
|
|
This caused us other code to incorrectly assume in dealing with a declaration when in fact it was dealing with a glob imported definition
|
|
|
|
|
|
The limit was introduced in https://github.com/rust-lang/rust-analyzer/pull/1408#discussion_r294059044 to avoid infinite cycles but it effectively caps the number of derefs to 10. Types like `ID3D12Device14` from the `windows` crate run into this because it derefs to `ID3D12Device13`, 13 to 12 and so on. Increasing it to 20 is a quick fix; a better cycle detection method would be nicer long term.
|
|
Ensure that all the fields that rust-analyzer understands are in the
manual, they all have doc comments, and they use consistent
punctuation (`;` rather than mixing `,` and `;`).
Whilst we're here, fix the `sysroot_src` example and add 2024 as a
legal value for Rust edition.
|
|
If the user doesn't have rustc on $PATH, rust-analyzer won't be able
to run `rustc --print cfg`. This isn't really an error, as
rust-analyzer can still proceed without it.
This is particularly noticeable when loading crates defined in a
rust-project.json. Until the configuration is loaded, the opened files
are briefly treated as detached files and users see this error.
Environments with rust-project.json generally have a sysroot and rustc
elsewhere, so the error confuses users.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I don't think my ranking is perfect, because it places them even behind snippet completions, but this is something.
|
|
|
|
Goto `Display::fmt` when invoked on `to_string`
|
|
|
|
fix: Fix missing upmapping in trait impls completion
|
|
This time, when completing the keyword (e.g. `fn` + whitespace).
The bug was actually a double-bug:
First, we did not resolve the impl in the macro-expanded file but in the real file, which of course cannot work.
Second, in analysis the whitespace was correlated with the `impl` and not the incomplete `fn`, which caused fake (where we insert an identifier after the whitespace) and real expansions to go out of sync, which failed analysis. The fix is to skip whitespaces in analysis.
|
|
|
|
|
|
|
|
|
|
fixes #18766
|
|
Properly record meaningful imports as re-exports in symbol index
|
|
feat: Add the ability to jump from `into` to `from` definitions
|
|
Extract variable assist triggers less eagerly
|
|
osiewicz/drop-outgoing-messages-on-background-thread
lsp-server: Drop outgoing messages on background thread
|
|
fix: Fix a bug where enum variants were not considered properly in type ns resolution
|