| Age | Commit message (Collapse) | Author | Lines |
|---|
|
minor: Fix outdated comment in hir-ty/generics.rs
|
|
|
|
Update chalk
|
|
|
|
`HygieneId` fits into `Binding`'s padding.
|
|
internal: Make predefined symbols `const` instead of `static`
|
|
Add semicolon to use
|
|
allow using `null` to unset an environment variable
|
|
feat: Parse generic consts
|
|
feat: parse `super let`
|
|
minor: simplify and enhance notable traits rendering
|
|
feat: Allow unsetting env vars in `server.extraEnv` config
|
|
|
|
|
|
|
|
|
|
|
|
This backs out commit 8497fc321cad420b923e15f600106f8e22324930.
|
|
This is necessary to correctly handle nested fields (`foo.bar`), see the comments in the code for explanation.
|
|
Now that they're const it's no longer needed.
Nothing manual was performed: only a regexp search of `sym::([\w][\w\d]*)\.clone\(\)` and replace by `sym::$1`.
|
|
Make them all `const`.
|
|
A lang team experiment, https://github.com/rust-lang/rust/issues/113521.
|
|
|
|
|
|
|
|
Also first line of default code blocks being used as the language instead of json
and fixes a missing `json` language in a doc comment code block.
|
|
|
|
internal: Make `HirFileId`, `EditionedFileId` and macro files Salsa struct
|
|
And make more queries non-interned.
Also flip the default for queries, now the default is to not intern and to intern a query you need to say `invoke_interned`.
|
|
this makes three changes:
- all callsites of `toolchain::command` are changed to use
`command(path, extra_env)`, instead of manually adding the env after
the fact.
- all `map<str, str>` are changed to `map<str, option<str>>`.
- `command` checks for None and calls `env_remove` if so.
this caught several places where environment variables weren't being
propagated:
- when running `rustc --print=target-libdir`
- when running `cargo rustc -- --print=target-spec-json`
- when running the custom DiscoverLinkedProjects config. I *think* this
is for use with non-cargo build systems, so I didn't change it.
|
|
previously, these would just silently be ignored. now they give a
warning such as:
```
invalid config values: /completion/snippets/custom: invalid type: null, expected a map; /cargo/extraEnv: invalid type: null, expected a string;
```
|
|
|
|
fix: Fix a panic when a trait method in an impl declares a lifetime parameter not in the trait declaration
|
|
|
|
internal: Support specific revisions for PGO
|
|
|
|
Previously it was ordered by what accidentally happened to be the crate graph order, which isn't sensible, plus it caused changes when any change was done to salsa IDs.
|
|
internal: Make hir-ty non-diagnostic queries transparent
|
|
That is, all queries that have a `with_diagnostic` variant.
Them being tracked was (maybe) needed before #19462, because back then diagnostics could refer `AstId`s (for macro types), but now they are no longer needed.
|
|
in the trait declaration
Shuffle the code a bit.
|
|
update libc
This is needed for https://github.com/rust-lang/rust/pull/138699#discussion_r2048603474
|
|
|
|
internal: Build MacOS AArch64 releases on that platform
|
|
fix: Fix a bug with predicate lowering of associated items
|
|
|
|
r=davidtwco,Urgau,traviscross
Stabilize `cfg_boolean_literals`
Closes #131204
`@rustbot` labels +T-lang +I-lang-nominated
This will end up conflicting with the test in #138293 so whichever doesn't land first will need updating
--
# Stabilization Report
## General design
### What is the RFC for this feature and what changes have occurred to the user-facing design since the RFC was finalized?
[RFC 3695](https://github.com/rust-lang/rfcs/pull/3695), none.
### What behavior are we committing to that has been controversial? Summarize the major arguments pro/con.
None
### Are there extensions to this feature that remain unstable? How do we know that we are not accidentally committing to those?
None
## Has a call-for-testing period been conducted? If so, what feedback was received?
Yes; only positive feedback was received.
## Implementation quality
### Summarize the major parts of the implementation and provide links into the code (or to PRs)
Implemented in [#131034](https://github.com/rust-lang/rust/pull/131034).
### Summarize existing test coverage of this feature
- [Basic usage, including `#[cfg()]`, `cfg!()` and `#[cfg_attr()]`](https://github.com/rust-lang/rust/blob/6d71251cf9e40326461f90f8ff9a7024706aea87/tests/ui/cfg/true-false.rs)
- [`--cfg=true/false` on the command line being accessible via `r#true/r#false`](https://github.com/rust-lang/rust/blob/6d71251cf9e40326461f90f8ff9a7024706aea87/tests/ui/cfg/raw-true-false.rs)
- [Interaction with the unstable `#[doc(cfg(..))]` feature](https://github.com/rust-lang/rust/tree/6d71251/tests/rustdoc-ui/cfg-boolean-literal.rs)
- [Denying `--check-cfg=cfg(true/false)`](https://github.com/rust-lang/rust/tree/6d71251/tests/ui/check-cfg/invalid-arguments.rs)
- Ensuring `--cfg false` on the command line doesn't change the meaning of `cfg(false)`: `tests/ui/cfg/cmdline-false.rs`
- Ensuring both `cfg(true)` and `cfg(false)` on the same item result in it being disabled: `tests/ui/cfg/both-true-false.rs`
### What outstanding bugs in the issue tracker involve this feature? Are they stabilization-blocking?
The above mentioned issue; it should not block as it interacts with another unstable feature.
### What FIXMEs are still in the code for that feature and why is it ok to leave them there?
None
### Summarize contributors to the feature by name for recognition and assuredness that people involved in the feature agree with stabilization
- `@clubby789` (RFC)
- `@Urgau` (Implementation in rustc)
### Which tools need to be adjusted to support this feature. Has this work been done?
`rustdoc`'s unstable`#[doc(cfg(..)]` has been updated to respect it. `cargo` has been updated with a forward compatibility lint to enable supporting it in cargo once stabilized.
## Type system and execution rules
### What updates are needed to the reference/specification? (link to PRs when they exist)
A few lines to be added to the reference for configuration predicates, specified in the RFC.
|
|
The essence of the bug is that bounds on `impl Trait` got lowered with incorrect bound vars, as if we were lowering the parent.
|
|
- realted to https://github.com/rust-lang/rust-analyzer/issues/9412#issuecomment-2810772246
|
|
minor: Fix signature of libc memory usage function on Linux
|
|
A soundness issue!
|
