rust/compiler/rustc_mir_dataflow/src/framework, branch stablehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=stable2025-07-11T08:56:50+00:00Remove support for SwitchInt edge effects in backward dataflow analyses2025-07-11T08:56:50+00:00Tomasz Miąskotomasz.miasko@gmail.com2025-07-11T06:43:16+00:00urn:sha1:5b6d661039116ea573652393938061a9a2a2c586
Those effects are untested and unused. Remove them along with
the implementation of `BasicBlocks::switch_sources`.
Call `get_switch_int_data` on a block with SwitchInt terminator2025-07-11T06:49:11+00:00Tomasz Miąskotomasz.miasko@gmail.com2025-07-11T06:10:16+00:00urn:sha1:011d4aa81f1d20b4923a01c7162caa5f0042b8ba
Fix a mix-up of a block with its predecessors in handling of SwitchInt
edge effects for backward analysis. Note that this functionality is
currently unused, so change has no practical impact.
Auto merge of #142707 - ashivaram23:drop_wildcard, r=dianqk2025-07-09T03:42:01+00:00borsbors@rust-lang.org2025-07-09T03:42:01+00:00urn:sha1:d350797b7e1a5b6952f5035cbad2a21613b32f6c
Apply effects to `otherwise` edge in dataflow analysis
This allows `ElaborateDrops` to remove drops when a `match` wildcard arm covers multiple no-Drop enum variants. It modifies dataflow analysis to update the `MaybeUninitializedPlaces` and `MaybeInitializedPlaces` data for a block reached through an `otherwise` edge.
Fixes rust-lang/rust#142705.
Apply effects to otherwise edge in dataflow analysis2025-07-08T23:15:05+00:00Amogh Shivaramashivaram264@gmail.com2025-07-08T23:15:05+00:00urn:sha1:c7ef03aeb7c33825e3d020c9e1791171e71cd445mir: Use the `new` method for `BasicBlockData`2025-06-29T12:39:13+00:00dianqkdianqk@dianqk.net2025-06-16T14:31:25+00:00urn:sha1:24e553e6bcfa329b04b93c0978e00b492224a255mir: Add a `new` method to `statement`2025-06-29T12:13:36+00:00dianqkdianqk@dianqk.net2025-06-08T07:30:18+00:00urn:sha1:9f9cd5e2837f57504b92b5acbadb48ff0cb9e29c
Avoid introducing a large number of changes when adding optional initialization fields.
Separate `Analysis` and `Results`.2025-04-24T01:36:07+00:00Nicholas Nethercoten.nethercote@gmail.com2025-04-18T00:46:20+00:00urn:sha1:92799b6f89d2d9bbfcb9b11d1bac57899d0bc435
`Results` contains and `Analysis` and an `EntryStates`. The unfortunate
thing about this is that the analysis needs to be mutable everywhere
(`&mut Analysis`) which forces the `Results` to be mutable everywhere,
even though `EntryStates` is immutable everywhere.
To fix this, this commit renames `Results` as `AnalysisAndResults`,
renames `EntryStates` as `Results`, and separates the analysis and
results as much as possible. (`AnalysisAndResults` doesn't get much use,
it's mostly there to facilitate method chaining of
`iterate_to_fixpoint`.)
`Results` is immutable everywhere, which:
- is a bit clearer on how the data is used,
- avoids an unnecessary clone of entry states in
`locals_live_across_suspend_points`, and
- moves the results outside the `RefCell` in Formatter.
The commit also reformulates `ResultsHandle` as the generic `CowMut`,
which is simpler than `ResultsHandle` because it doesn't need the
`'tcx` lifetime and the trait bounds. It also which sits nicely
alongside the new use of `Cow` in `ResultsCursor`.
Pass `Analysis` to `visit_*` instead of `Results`.2025-04-24T01:34:06+00:00Nicholas Nethercoten.nethercote@gmail.com2025-04-03T06:37:55+00:00urn:sha1:4ff55588d33366d0572c1865b43dec8ac00237b1
Every `Results` contains an `Analysis`, but these methods only need the
`Analysis`. No point passing them more data than they need.
Remove unnecessary lifetime on `ResultsVisitor`.2025-04-22T00:08:05+00:00Nicholas Nethercoten.nethercote@gmail.com2025-04-22T00:08:05+00:00urn:sha1:521b379705bcdd9ea41e8bce56bfd16ba1b90703Remove unused `ResultsCursor` methods.2025-04-21T23:46:24+00:00Nicholas Nethercoten.nethercote@gmail.com2025-04-21T00:25:32+00:00urn:sha1:3bd1e1484f23e6062feaa6106ce73e459d892812