| Age | Commit message (Collapse) | Author | Lines |
|
Make -Ztrack-diagnostics emit like a note
[#t-compiler/diagnostics > Rendering -Ztrack-diagnostics like a note](https://rust-lang.zulipchat.com/#narrow/channel/147480-t-compiler.2Fdiagnostics/topic/Rendering.20-Ztrack-diagnostics.20like.20a.20note/with/526608647)
As discussed on the Zulip thread above, I want to make `-Ztrack-diagnostics` emit like a `note`. This is because I find its current output jarring, and the fact that it gets rendered completely left-aligned, [even in the middle of a snippet](https://github.com/rust-lang/rust/blob/86e05cd300fac9e83e812c4d46582b48db780d8f/tests/ui/track-diagnostics/track6.stderr), seems like something that should be changed. Turning it into a `note` seems like the best choice, as it would align it with the rest of the output, and `note` is already used for somewhat similar things, like seeing why a lint was fired.
---
Note: turning `-Ztrack-diagnostics` into a `note` will also make `annotate-snippets` API a bit cleaner
|
|
|
|
Improve flycheck and build script progress reporting
|
|
|
|
|
|
|
|
Fix: Resolve HIR display length issues and improve adjustment tooltips
|
|
Co-authored-by: Giga Bowser <45986823+Giga-Bowser@users.noreply.github.com>
|
|
fix: Honor `rust-analyzer.cargo.noDeps` option when fetching sysroot metadata
|
|
Migrate `unmerge_match_arm` Assist to use `SyntaxEditor`
|
|
fix: Fix some things with builtin derives
|
|
|
|
|
|
Replace kw_span by full span for generic const parameters.
Small simplification extracted from https://github.com/rust-lang/rust/pull/127241
|
|
load_workspace`
|
|
1. Err on unions on derive where it's required.
2. Err on `#[derive(Default)]` on enums without `#[default]` variant.
3. Don't add where bounds `T: Default` when expanding `Default` on enums (structs need that, enums not).
Also, because I was annoyed by that, in minicore, add a way to filter on multiple flags in the line-filter (`// :`). This is required for the `Debug` and `Hash` derives, because the derive should be in the prelude but the trait not.
|
|
Rollup of 5 pull requests
Successful merges:
- rust-lang/rust#141831 (rustdoc: fix attrs of locally reexported foreign items)
- rust-lang/rust#143364 (don't include `.md` in title)
- rust-lang/rust#143369 (Various refactorings to the metadata loader)
- rust-lang/rust#143379 (Post {beta,stable}-accepted notifications to compiler/bootstrap backport zulip channels on `{beta,stable}-accepted` label application)
- rust-lang/rust#143384 (Update browser-ui-test version to `0.21.1`)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
Update browser-ui-test version to `0.21.1`
One day I'll find time and motivation to use `package.json` instead. :laughing:
r? `@Kobzol`
|
|
Signed-off-by: Hayashi Mikihiro <34ttrweoewiwe28@gmail.com>
|
|
Weekly `cargo update`
Automation to keep dependencies in `Cargo.lock` current.
The following is the output from `cargo update`:
```txt
compiler & tools dependencies:
Locking 23 packages to latest compatible versions
Updating anstyle-svg v0.1.8 -> v0.1.9
Updating autocfg v1.4.0 -> v1.5.0
Updating bumpalo v3.18.1 -> v3.19.0
Updating derive-where v1.4.0 -> v1.5.0
Updating errno v0.3.12 -> v0.3.13
Updating indexmap v2.9.0 -> v2.10.0
Updating libredox v0.1.3 -> v0.1.4
Updating owo-colors v4.2.1 -> v4.2.2
Updating pest v2.8.0 -> v2.8.1
Updating pest_derive v2.8.0 -> v2.8.1
Updating pest_generator v2.8.0 -> v2.8.1
Updating pest_meta v2.8.0 -> v2.8.1
Updating r-efi v5.2.0 -> v5.3.0
Updating rustc-build-sysroot v0.5.8 -> v0.5.9
Updating slab v0.4.9 -> v0.4.10
Updating syn v2.0.103 -> v2.0.104
Adding toml v0.8.23
Adding toml_edit v0.22.27
Adding toml_write v0.1.2
Updating tracing-attributes v0.1.29 -> v0.1.30
Updating xattr v1.5.0 -> v1.5.1
Updating zerocopy v0.8.25 -> v0.8.26
Updating zerocopy-derive v0.8.25 -> v0.8.26
note: pass `--verbose` to see 39 unchanged dependencies behind latest
library dependencies:
Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 3 unchanged dependencies behind latest
rustbook dependencies:
Locking 21 packages to latest compatible versions
Updating autocfg v1.4.0 -> v1.5.0
Updating bumpalo v3.18.1 -> v3.19.0
Updating errno v0.3.12 -> v0.3.13
Updating indexmap v2.9.0 -> v2.10.0
Updating markup5ever v0.16.1 -> v0.16.2
Updating pest v2.8.0 -> v2.8.1
Updating pest_derive v2.8.0 -> v2.8.1
Updating pest_generator v2.8.0 -> v2.8.1
Updating pest_meta v2.8.0 -> v2.8.1
Updating r-efi v5.2.0 -> v5.3.0
Updating syn v2.0.103 -> v2.0.104
Adding windows-sys v0.60.2
Adding windows-targets v0.53.2
Adding windows_aarch64_gnullvm v0.53.0
Adding windows_aarch64_msvc v0.53.0
Adding windows_i686_gnu v0.53.0
Adding windows_i686_gnullvm v0.53.0
Adding windows_i686_msvc v0.53.0
Adding windows_x86_64_gnu v0.53.0
Adding windows_x86_64_gnullvm v0.53.0
Adding windows_x86_64_msvc v0.53.0
```
|
|
compiler & tools dependencies:
Locking 23 packages to latest compatible versions
Updating anstyle-svg v0.1.8 -> v0.1.9
Updating autocfg v1.4.0 -> v1.5.0
Updating bumpalo v3.18.1 -> v3.19.0
Updating derive-where v1.4.0 -> v1.5.0
Updating errno v0.3.12 -> v0.3.13
Updating indexmap v2.9.0 -> v2.10.0
Updating libredox v0.1.3 -> v0.1.4
Updating owo-colors v4.2.1 -> v4.2.2
Updating pest v2.8.0 -> v2.8.1
Updating pest_derive v2.8.0 -> v2.8.1
Updating pest_generator v2.8.0 -> v2.8.1
Updating pest_meta v2.8.0 -> v2.8.1
Updating r-efi v5.2.0 -> v5.3.0
Updating rustc-build-sysroot v0.5.8 -> v0.5.9
Updating slab v0.4.9 -> v0.4.10
Updating syn v2.0.103 -> v2.0.104
Adding toml v0.8.23
Adding toml_edit v0.22.27
Adding toml_write v0.1.2
Updating tracing-attributes v0.1.29 -> v0.1.30
Updating xattr v1.5.0 -> v1.5.1
Updating zerocopy v0.8.25 -> v0.8.26
Updating zerocopy-derive v0.8.25 -> v0.8.26
note: pass `--verbose` to see 39 unchanged dependencies behind latest
library dependencies:
Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 3 unchanged dependencies behind latest
rustbook dependencies:
Locking 21 packages to latest compatible versions
Updating autocfg v1.4.0 -> v1.5.0
Updating bumpalo v3.18.1 -> v3.19.0
Updating errno v0.3.12 -> v0.3.13
Updating indexmap v2.9.0 -> v2.10.0
Updating markup5ever v0.16.1 -> v0.16.2
Updating pest v2.8.0 -> v2.8.1
Updating pest_derive v2.8.0 -> v2.8.1
Updating pest_generator v2.8.0 -> v2.8.1
Updating pest_meta v2.8.0 -> v2.8.1
Updating r-efi v5.2.0 -> v5.3.0
Updating syn v2.0.103 -> v2.0.104
Adding windows-sys v0.60.2
Adding windows-targets v0.53.2
Adding windows_aarch64_gnullvm v0.53.0
Adding windows_aarch64_msvc v0.53.0
Adding windows_i686_gnu v0.53.0
Adding windows_i686_gnullvm v0.53.0
Adding windows_i686_msvc v0.53.0
Adding windows_x86_64_gnu v0.53.0
Adding windows_x86_64_gnullvm v0.53.0
Adding windows_x86_64_msvc v0.53.0
|
|
|
|
|
|
fix: Incorrect closure capturing for let exprs
|
|
fix: resolve item in match bind
|
|
|
|
Signed-off-by: Hayashi Mikihiro <34ttrweoewiwe28@gmail.com>
|
|
|
|
|
|
fix: Improve diagnostic ranges for `macro_calls!`
|
|
We used to point to the entire macro call including its token tree if we couldn't upmap the diagnostic to the input
This generally makes things very noisy as the entire macro call will turn red on errors.
Instead, we now macro the path and `!` (bang) token as the error source range which is a lot nicer on the eyes.
|
|
setup typos check in CI
This allows to check typos in CI, currently for compiler only (to reduce commit size with fixes). With current setup, exclude list is quite short, so it worth trying?
Also includes commits with actual typo fixes.
MCP: https://github.com/rust-lang/compiler-team/issues/817
typos check currently turned for:
* ./compiler
* ./library
* ./src/bootstrap
* ./src/librustdoc
After merging, PRs which enables checks for other crates (tools) can be implemented too.
Found typos will **not break** other jobs immediately: (tests, building compiler for perf run). Job will be marked as red on completion in ~ 20 secs, so you will not forget to fix it whenever you want, before merging pr.
Check typos: `python x.py test tidy --extra-checks=spellcheck`
Apply typo fixes: `python x.py test tidy --extra-checks=spellcheck:fix` (in case if there only 1 suggestion of each typo)
Current fail in this pr is expected and shows how typo errors emitted. Commit with error will be removed after r+.
|
|
Always couple `--compile-time-deps` with
|
|
`--all-targets` coupled with `--compile-time-deps` will never actually build binaries and so it won't fail for targets where libtest is missing
|
|
fix: Do not warn about proc-macro srv when sysroot is missing
|
|
|
|
Re-enable fixpoint iteration for variance computation
|
|
|
|
|
|
|
|
Bump salsa
|
|
|
|
Workaround missing none group support in builtin macros
|
|
|
|
Restructure proc-macro loading erros, differentiate hard error property on kind
|
|
|
|
Rename `mingw-*` CI jobs to `pr-*`
The name `mingw` confuses people because these CI jobs now do much more than just cross-compile to mingw.
This is basically a find/replace. I chose the name `pr-` because it's job is to do general PR checks,
|
|
|
|
miri: improve errors for type validity assertion failures
Miri has pretty nice errors for type validity violations, printing which field in the type the problem occurs at and so on.
However, we don't see these errors when using e.g. `mem::zeroed` as that uses `assert_zero_valid` to bail out before Miri can detect the UB.
Similar to what we did with `@saethlin's` UB checks, I think we should disable such language UB checks in Miri so that we can get better error messages. If we go for this we should probably say this in the intrinsic docs as well so that people don't think they can rely on these intrinsics catching anything.
Furthermore, I slightly changed `MaybeUninit::assume_init` so that the `.value` field does not show up in error messages any more.
`@rust-lang/miri` what do you think?
|