| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Improve keyword completion for 'let' and 'let mut'
|
|
Highlight unsafe operations as unsafe, not definitions
|
|
|
|
|
|
Use `size_of` from the prelude instead of imported
|
|
Use `std::mem::{size_of, size_of_val, align_of, align_of_val}` from the
prelude instead of importing or qualifying them.
These functions were added to all preludes in Rust 1.80.
|
|
|
|
Twiddle with the `rustup` invocation on CI
|
|
feat: Add diagnostic for dangling dyn and impl
|
|
|
|
|
|
|
|
Bump minimum supported toolchain to 1.82
|
|
|
|
Support tuple struct patterns for expand_rest_pattern assist
|
|
Allow unsetting default cfgs
|
|
Warn when the used toolchain looks too old for rust-analyzer
|
|
|
|
- Adds dangling impl diagnostics
- Rename validation test from dangling_impl to dangling_iml_ref
|
|
minor: sync from downstream
|
|
|
|
|
|
|
|
completion-ref-matching
|
|
Optimize empty provenance range checks.
Currently it gets the pointers in the range and checks if the result is empty, but it can be done faster if you combine those two steps.
r? `@oli-obk`
|
|
Update to LLVM 20 rc 3
Fixes a compiler-builtins miscompile (see https://github.com/rust-lang/compiler-builtins/pull/760).
|
|
Add `identifier` to pull diagnostic LSP capabilities
|
|
This field in the server capabilities instructs the client to maintain
the diagnostics received from a `textDocument/diagnostic` pull request
as a separate set from other diagnostics: namely those sent with classic
"push" diagnostics, `textDocument/publishDiagnostic`. rust-analyzer
emits "native" diagnostics (computed by rust-analyzer itself) in pull
diagnostics and separately emits cargo-based diagnostics with push, so
push and pull diagnostics should be different sets. Setting this field
instructs the client to avoid clearing push diagnostics when new pull
diagnostics arrive and vice versa.
|
|
minor: Fix transparent diagnostics
|
|
|
|
|
|
|
|
r=GuillaumeGomez
`librustdoc`: return `impl fmt::Display` in more places instead of writing to strings
Continuation of #136784 , another attempt at landing the larger parts of #136748 .
I'd like to, gradually, make all of the building blocks for rendering docs in `librustdoc` return `impl fmt::Display` instead of returning `Strings`, or receiving a `&mut String` (or `&mut impl fmt::Write`). Another smaller end goal is to be able to get rid of [`write_str`](https://github.com/rust-lang/rust/blob/8dac72bb1d12b2649acd0c190e41524f83da5683/src/librustdoc/html/format.rs#L40-L42).
This PR is a large step in that direction.
Most of the changes are quite mechanical, and split up into separate commits for easier reviewing (hopefully). I took `print_item` and then started by converting all the functions it called (and their dependencies), and the last commit does the conversion for `print_item` itself. Ignoring whitespace should make reviewing a bit easier.
And most importantly, perf run shows pretty good results locally, hopefully CI will also show green 😁
r? `@GuillaumeGomez` , if you feel like it.
|
|
Rewrite the `ci.py` script in Rust
It would seem that I would learn by now that any script written in Python will become unmaintainable sooner or later, but alas..
r? `@marcoieni`
try-job: aarch64-gnu
try-job: dist-x86_64-linux-alt
try-job: x86_64-msvc-ext2
Fixes: https://github.com/rust-lang/rust/issues/137013
|
|
|
|
Add flip or-pattern assist
|
|
internal: Migrate `convert_bool_then` to `SyntaxEditor`
|
|
|
|
Rollup of 10 pull requests
Successful merges:
- #137804 (rename BackendRepr::Vector → SimdVector)
- #137807 (Fully qualify `Result` in generated doctest code)
- #137809 (Use correct error message casing for `io::const_error`s)
- #137818 (tests: adapt for LLVM 21 changes)
- #137822 (Update query normalizer docs to not position it as the greatest pioneer in the space of normalization)
- #137824 (Tweak invalid RTN errors)
- #137828 (Fix inaccurate `std::intrinsics::simd` documentation)
- #137830 (Fix link failure on AVR (incompatible ISA error))
- #137837 (Update `const_conditions` and `explicit_implied_const_bounds` docs)
- #137840 (triagebot: only ping me for constck)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
Clippy subtree update
? `@Manishearth`
Cargo.lock change because of Clippy version bump and rustc_tool_utils new release.
Fixes #137640
Would be nice, if we could this merged before nightly is being build, so that this ICE is fixed tomorrow.
|
|
Remove syntax editing from parenthesis computation
|
|
internal: Cleanup some syntax highlighting things
|
|
|
|
|
|
|
|
|
|
|
|
triagebot: only ping me for constck
Per the [Zulip thread](https://rust-lang.zulipchat.com/#narrow/channel/146212-t-compiler.2Fconst-eval/topic/rustbot.20pings).
cc `@rust-lang/wg-const-eval.`
|
|
Update `const_conditions` and `explicit_implied_const_bounds` docs
Move documentation to query definitions, and add docs to `explicit_implied_const_bounds`.
r? project-const-traits
|
|
Fix link failure on AVR (incompatible ISA error)
Fixes #137739. A reproducer of the issue is present there. I believe the root cause was introducing the avr-none target (which has no CPU by default) while also trying to get the ISA revision from the target spec. This commit uses the `target-cpu` option instead, which is already required to be present for the target.
r? compiler
cc ``@Patryk27``
|
