| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
|
Rollup of 8 pull requests
Successful merges:
- rust-lang/rust#140715 (Clarify &mut-methods' docs on sync::OnceLock)
- rust-lang/rust#141677 (Async drop - type instead of async drop fn, fixes rust-lang/rust#140484)
- rust-lang/rust#141741 (Overhaul `UsePath`)
- rust-lang/rust#141873 (Fixed a typo in `ManuallyDrop`'s doc)
- rust-lang/rust#141876 (Don't declare variables in `ExprKind::Let` in invalid positions)
- rust-lang/rust#141886 (Add missing 2015 edition directives)
- rust-lang/rust#141889 (Add missing `dyn` keywords to tests that do not test for them)
- rust-lang/rust#141891 (Fix borrowck mentioning a name from an external macro we (deliberately) don't save)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
Add a quickfix for accessing a private field of a struct
|
|
fix: Cycle handlers for `HirDatabase::infer, const_param_ty_with_diagnostics`
|
|
Enable Assist edit for tuple<->named struct for the struct and visiblity keywords
|
|
|
|
Overhaul `UsePath`
It currently uses `SmallVec<[Res; 3]>` which is really weird. Details in the individual commits.
r? `@petrochenkov`
|
|
|
|
|
|
tools-aux ci runner: also cross-test doctests in Miri
Miri now supports running doctests across different targets. Let's use that to run the std doctests on aarch64-apple-darwin, i686-pc-windows-msvc.
try-job: x86_64-gnu-aux
|
|
|
|
|
|
`UsePath` contains a `SmallVec<[Res; 3]>`. This holds up to three `Res`
results, one per namespace (type, value, or macro). `lower_import_res`
takes a `PerNS<Option<Res<NodeId>>>` result and lowers it into the
`SmallVec`. This is pretty weird. The input `PerNS` makes it clear which
`Res` belongs to which namespace, but the `SmallVec` throws that
information away.
And code that operates on the `SmallVec` tends to use iteration (or even
just grabbing the first entry!) without knowing which namespace the
`Res` belongs to. Even weirder! Also, `SmallVec` is an overly flexible
type to use here, because it can contain any number of elements (even
though it's optimized for 3 in this case).
This commit changes `UsePath` so it also contains a
`PerNS<Option<Res<HirId>>>`. This type preserves more information and is
more self-documenting. The commit also changes a lot of the use sites to
access the result for a particular namespace. E.g. if you're looking up
a trait, it will be in the `Res` for the type namespace if it's present;
it's silly to look in the `Res` for the value namespace or macro
namespace. Overall I find the new code much easier to understand.
However, some use sites still iterate. These now use `present_items`
because that filters out the `None` results.
Also, `redundant_pub_crate.rs` gets a bigger change. A
`UseKind:ListStem` item gets no `Res` results, which means the old `all`
call in `is_not_macro_export` would succeed (because `all` succeeds on
an empty iterator) and the `ListStem` would be ignored. This is what we
want, but was more by luck than design. The new code detects `ListStem`
explicitly. The commit generalizes the name of that function
accordingly.
Finally, the commit also removes the `use_path` arena, because
`PerNS<Option<Res>>` impls `Copy` (unlike `SmallVec`) and it can be
allocated in the arena shared by all `Copy` types.
|
|
|
|
Rollup of 5 pull requests
Successful merges:
- rust-lang/rust#141767 (ci: use free runner for aarch64-gnu-llvm-19-1 PR job)
- rust-lang/rust#141858 (Fix typo in `StructuralPartialEq` docs)
- rust-lang/rust#141865 (Optionally don't steal the THIR)
- rust-lang/rust#141874 (add f16_epsilon and f128_epsilon diagnostic items)
- rust-lang/rust#141904 (test-float-parse: apply `cfg(not(bootstrap))`)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
|
|
Rollup of 6 pull requests
Successful merges:
- rust-lang/rust#141884 (allow macro_use as first segment)
- rust-lang/rust#141885 ([RTE-484] Update SGX maintainers)
- rust-lang/rust#141892 (Fix false positive lint error from no_implicit_prelude attr)
- rust-lang/rust#141894 (rustc-dev-guide subtree update)
- rust-lang/rust#141895 (tshepang has a new email)
- rust-lang/rust#141897 (Fix citool tests when executed locally)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
|
|
Simplify long sentence
|
|
|
|
Fix some warning blocks that contain Markdown
|
|
Contents inside of an HTML element only get interpreted as Markdown
(as opposed to HTML) if its separated from the HTML tags with line breaks.
|
|
Add title and toc to Async chapter
|
|
This is standard for other chapters.
|
|
|
|
|
|
|
|
symbol
Co-authored-by: Jake Goulding <jake.goulding@integer32.com>
|
|
test-float-parse: apply `cfg(not(bootstrap))`
Prior to stage 0 redesign, `test-float-parse` ran against in-tree std but now it runs against beta std. `f16::FromStr` is only present in in-tree std and not yet beta std, so apply `cfg(not(bootstrap))` gating to unbrick `./x check --stage=0`.
Fixes rust-lang/rust#141900.
`./x check --stage=0` in CI is intended for follow-up.
r? `@Mark-Simulacrum` (or bootstrap/libs)
cc `@tgross35`
|
|
Optionally don't steal the THIR
The THIR being stolen is a recurrent pain for authors of rustc drivers. This makes it optional, so that the `thir_body` query can still be used after analysis of the crate has completed.
|
|
ci: use free runner for aarch64-gnu-llvm-19-1 PR job
|
|
|
|
Fix citool tests when executed locally
They couldn't be executed locally before due to some additional environment reads.
I also investigated the annoying rebuilds that we see on CI all the time, and they are caused by `ring`'s build script. It should be fixed in the next ring release (https://github.com/briansmith/ring/issues/2525), so we can just wait for that and then update `ring`.
r? `@marcoieni`
|
|
rustc-dev-guide subtree update
r? `@ghost`
|
|
r=Noratrieb
[RTE-484] Update SGX maintainers
`@mzohreva` is no longer with Fortanix. We need to change the SGX maintainers accordingly.
|
|
Clippy subtree update
r? `@Manishearth`
|
|
Prior to stage 0 redesign, `test-float-parse` ran against in-tree std
but now it runs against beta std. `f16::FromStr` were only present in
in-tree std and not yet beta std, so apply `cfg(not(bootstrap))` gating
to unbrick `./x check --stage=0`.
|
|
|
|
|
|
|
|
They couldn't be executed locally before due to some additional environment reads.
|
|
|
|
|
|
|
|
The Rust source code previously mised ProjectJson and JsonProject,
and the TypeScript definition didn't match either.
Use 'ProjectJson' everywhere. This is purely an internal change.
|
|
Fix link to GatherBorrows
|
|
Add opaque type attributes
|
