| Age | Commit message (Collapse) | Author | Lines |
|---|
|
fix: Fix `ItemScope` not recording glob imports
|
|
Check cfg when collecting macro defs
|
|
This caused us other code to incorrectly assume in dealing with a declaration when in fact it was dealing with a glob imported definition
|
|
|
|
minor: Rephrase comment
|
|
|
|
increase `AUTODEREF_RECURSION_LIMIT` to 20
|
|
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.
|
|
manual: Document all rust-project.json fields
|
|
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.
|
|
fix: Sort completion items that skip `await` and `iter()` behind those that don't
|
|
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`
|
|
internal: Cleanup `Name` string rendering
|
|
|
|
fix: Fix missing upmapping in trait impls completion
|
|
fix: Only refresh syntax tree view when the active document changes
|
|
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.
|
|
|
|
|
|
internal: Move dual blanket impl logic from source analyzer to goto_def
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
proc-macro-srv: make usage of RTLD_DEEPBIND portable
|
|
minor: Sync from downstream
|
|
the constant is wrong on some platforms (e.g., on mips64el it's 0x10, and 0x8
is RTLD_NOLOAD which makes all this functionality broken), the libc crate takes
care of those differences for us.
fallback to not setting the flag in non-glibc environments - some of them might
have support for it using a different value that we don't know about, and some
of them lack it entirely.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
|
|
|
|
|
|
|
|
Miri subtree update
r? `@ghost`
|
|
Automatic Rustup
|
|
|
|
Weekly `cargo update`
Automation to keep dependencies in `Cargo.lock` current.
The following is the output from `cargo update`:
```txt
compiler & tools dependencies:
Locking 13 packages to latest compatible versions
Updating anstyle-wincon v3.0.6 -> v3.0.7
Updating bitflags v2.7.0 -> v2.8.0
Updating chrono-tz v0.10.0 -> v0.10.1
Updating js-sys v0.3.76 -> v0.3.77
Updating log v0.4.22 -> v0.4.25
Updating miniz_oxide v0.8.2 -> v0.8.3
Updating uuid v1.11.1 -> v1.12.0
Updating valuable v0.1.0 -> v0.1.1
Updating wasm-bindgen v0.2.99 -> v0.2.100
Updating wasm-bindgen-backend v0.2.99 -> v0.2.100
Updating wasm-bindgen-macro v0.2.99 -> v0.2.100
Updating wasm-bindgen-macro-support v0.2.99 -> v0.2.100
Updating wasm-bindgen-shared v0.2.99 -> v0.2.100
note: pass `--verbose` to see 41 unchanged dependencies behind latest
library dependencies:
Locking 1 package to latest compatible version
Updating miniz_oxide v0.8.2 -> v0.8.3
note: pass `--verbose` to see 4 unchanged dependencies behind latest
rustbook dependencies:
Locking 12 packages to latest compatible versions
Updating anstyle-wincon v3.0.6 -> v3.0.7
Updating bitflags v2.7.0 -> v2.8.0
Updating cc v1.2.8 -> v1.2.10
Updating js-sys v0.3.76 -> v0.3.77
Updating log v0.4.22 -> v0.4.25
Updating miniz_oxide v0.8.2 -> v0.8.3
Adding rustversion v1.0.19
Updating wasm-bindgen v0.2.99 -> v0.2.100
Updating wasm-bindgen-backend v0.2.99 -> v0.2.100
Updating wasm-bindgen-macro v0.2.99 -> v0.2.100
Updating wasm-bindgen-macro-support v0.2.99 -> v0.2.100
Updating wasm-bindgen-shared v0.2.99 -> v0.2.100
```
|
|
Rollup of 5 pull requests
Successful merges:
- #134858 (Provide structured suggestion for `#![feature(..)]` in more cases)
- #135679 (create an issue template for bootstrap)
- #135685 (Remove unused `item-row` CSS class)
- #135716 (Don't skip argument parsing when running `rustc` with no arguments)
- #135723 (Fix dev guide docs for error-pattern)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
Fix dev guide docs for error-pattern
I know it would have made more sense to make this PR to the dev guide repo but I had already made the fix before I realized that.
r? `@jieyouxu`
|
|
Don't skip argument parsing when running `rustc` with no arguments
Setting up the argument parser to parse no arguments is a tiny bit of wasted work, but avoids an otherwise-unnecessary special case, in a scenario (printing a help message and quitting) where perf at this scale really doesn't matter anyway.
In particular, this lets us avoid having to deal with multiple different APIs to determine whether the compiler is nightly or not.
---
This special-case handling for rustc with no arguments is very very old (long predating 1.0), and used to be much simpler, without any need to set up boolean values to handle various conditional cases. So I don't think it was ever explicitly decided that having this special case was worth the extra complexity; it just started out simple and accumulated complexity over time.
|
|
Remove unused `item-row` CSS class
Seems like a CSS class we forgot to remove at some point.
r? `@notriddle`
|
|
create an issue template for bootstrap
Resolves #135593
cc `@rust-lang/bootstrap`
|
