| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
Stabilize try_reserve
Stabilization PR for the [`try_reserve` feature](https://github.com/rust-lang/rust/issues/48043#issuecomment-898040475).
|
|
Stabilize `const_panic`
Closes #51999
FCP completed in #89006
```@rustbot``` label +A-const-eval +A-const-fn +T-lang
cc ```@oli-obk``` for review (not `r?`'ing as not on lang team)
|
|
|
|
|
|
|
|
|
|
Consistent big O notation
This makes the big O time complexity notation in places with markdown support more consistent.
Inspired by #89210
|
|
awd
|
|
|
|
Stabilize `Iterator::map_while`
Per the FCP: https://github.com/rust-lang/rust/issues/68537#issuecomment-922385035
This PR stabilizes `Iterator::map_while` and `iter::MapWhile` in Rust 1.57.
|
|
This results in a lot less assembly
|
|
|
|
Rework DepthFirstSearch API
This expands the API to be more flexible, allowing for more visitation patterns
on graphs. This will be useful to avoid extra datasets (and allocations) in
cases where the expanded DFS API is sufficient.
This also fixes a bug with the previous DFS constructor, which left the start
node not marked as visited (even though it was immediately returned).
Commit written by ```@nikomatsakis``` originally, cherry picked from several commits in work on never type stabilization, but stands alone.
|
|
Local variables can never be exported.
|
|
|
|
This expands the API to be more flexible, allowing for more visitation patterns
on graphs. This will be useful to avoid extra datasets (and allocations) in
cases where the expanded DFS API is sufficient.
This also fixes a bug with the previous DFS constructor, which left the start
node not marked as visited (even though it was immediately returned).
|
|
Remove SmallVector mention
SmallVector is long gone, as it's been first replaced
by OneVector in commit e5e6375352636360add297c1f5a1f37ce71506e9,
which then has been removed entirely in favour of SmallVec in
commit 130a32fa7259d348dc3a684b38e688da398c30bb.
|
|
SmallVector is long gone, as it's been first replaced
by OneVector in commit e5e6375352636360add297c1f5a1f37ce71506e9,
which then has been removed entirely in favour of SmallVec in
commit 130a32fa7259d348dc3a684b38e688da398c30bb.
|
|
Fix the flock fallback implementation
|
|
Use MaybeUninit::write in functor.rs
MaybeUninit::write is stable as of 1.55.0.
|
|
MaybeUninit::write is stable as of 1.55.0.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Improve `get_by_key_enumerated` more
Follow-up of #86392, this applies the suggestions by `@m-ou-se.`
r? `@m-ou-se`
|
|
Otherwise is a bug that we want to uncover.
|
|
|
|
|
|
|
|
Make mir borrowck's use of opaque types independent of the typeck query's result
fixes #87218
fixes #86465
we used to use the typeck results only to generate an obligation for the mir borrowck type to be equal to the typeck result.
When i removed the `fixup_opaque_types` function in #87200, I exposed a bug that showed that mir borrowck can't doesn't get enough information from typeck in order to build the correct lifetime mapping from opaque type usage to the actual concrete type. We therefor now fully compute the information within mir borrowck (we already did that, but we only used it to verify the typeck result) and stop using the typeck information.
We will likely be able to remove most opaque type information from the borrowck results in the future and just have all current callers use the mir borrowck result instead.
r? `@spastorino`
|
|
|
|
It used to allow you to mutate the key, even though that can invalidate the map by creating duplicate keys.
|
|
Profile incremental compilation hashing fingerprints
Adds profiling instrumentation for the hashing of incremental compilation fingerprints per query.
This will eventually feed into the `measureme` and `rustc-perf` infrastructure for tracking if computing hashes changes over time.
TODOs:
* [x] Address the FIXME where we are including node interning in the hash timing.
* [ ] Update measureme/summarize to handle this new data: https://github.com/rust-lang/measureme/pull/166
* [ ] ~Update rustc-perf to handle the new data from measureme~ (will be done at a later time)
r? `@ghost`
cc `@michaelwoerister`
|
|
|
|
|
|
|
|
|
|
Remove `#[allow(unused_lifetimes)]` which is now unnecessary
Seems FP has been fixed, it doesn't need `#[allow(unused_lifetimes)]` anymore.
|
|
|
|
|
|
Don't use a generator for BoxedResolver
The generator is non-trivial and requires unsafe code anyway. Using regular unsafe code without a generator is much easier to follow.
Based on #85810 as it touches rustc_interface too.
|
|
|
|
|