rust/compiler/rustc_mir_dataflow/src/move_paths, branch try

Greatly simplify lifetime captures in edition 2024

2025-02-22T22:24:52+00:00

Remove `rustc_middle::mir::tcx` module.

2025-02-18T23:26:05+00:00

This is a really weird module. For example, what does `tcx` in `rustc_middle::mir::tcx::PlaceTy` mean? The answer is "not much". The top-level module comment says: > Methods for the various MIR types. These are intended for use after > building is complete. Awfully broad for a module that has a handful of impl blocks for some MIR types, none of which really relates to `TyCtxt`. `git blame` indicates the comment is ancient, from 2015, and made sense then. This module is now vestigial. This commit removes it and moves all the code within into `rustc_middle::mir::statement`. Some specifics: - `Place`, `PlaceRef`, `Rvalue`, `Operand`, `BorrowKind`: they all have `impl` blocks in both the `tcx` and `statement` modules. The commit merges the former into the latter. - `BinOp`, `UnOp`: they only have `impl` blocks in `tcx`. The commit moves these into `statement`. - `PlaceTy`, `RvalueInitializationState`: they are defined in `tcx`. This commit moves them into `statement` *and* makes them available in `mir::*`, like many other MIR types.

Contracts core intrinsics.

2025-02-03T20:53:57+00:00

These are hooks to: 1. control whether contract checks are run 2. allow 3rd party tools to intercept and reintepret the results of running contracts.

Implement MIR, CTFE, and codegen for unsafe binders

2025-01-31T17:19:53+00:00

Revert "Auto merge of #134330 - scottmcm:no-more-rvalue-len, r=matthewjasper"

2025-01-18T22:09:34+00:00

This reverts commit e108481f74ff123ad98a63bd107a18d13035b275, reversing changes made to 303e8bd768526a5812bb1776e798e829ddb7d3ca.

Auto merge of #134625 - compiler-errors:unsafe-binders-ty, r=oli-obk

2024-12-24T00:51:51+00:00

Begin to implement type system layer of unsafe binders Mostly TODOs, but there's a lot of match arms that are basically just noops so I wanted to split these out before I put up the MIR lowering/projection part of this logic. r? oli-obk Tracking: - https://github.com/rust-lang/rust/issues/130516

Begin to implement type system layer of unsafe binders

2024-12-22T21:57:57+00:00

Delete `Rvalue::Len`

2024-12-22T14:12:39+00:00

Everything's moved to `PtrMetadata` instead.

Simplify `rustc_mir_dataflow::abs_domain`.

2024-12-10T23:45:47+00:00

`rustc_mir_dataflow` has a typedef `AbstractElem` that is equal to `ProjectionElem`. `AbstractOperand` and `AbstractType` are both unit types. There is also has a trait `Lift` to convert a `PlaceElem` to an `AbstractElem`. But `rustc_mir_middle` already has a typedef `ProjectionKind` that is equal to `ProjectionElem<(), ()>`, which is equivalent to `AbstractElem`. So this commit reuses `ProjectionKind` in `rustc_mir_dataflow`, removes `AbstractElem`, and simplifies the `Lift` trait.

reduce false positives of tail-expr-drop-order from consumed values

2024-11-20T12:53:11+00:00

take 2 open up coroutines tweak the wordings the lint works up until 2021 We were missing one case, for ADTs, which was causing `Result` to yield incorrect results. only include field spans with significant types deduplicate and eliminate field spans switch to emit spans to impl Drops Co-authored-by: Niko Matsakis collect drops instead of taking liveness diff apply some suggestions and add explantory notes small fix on the cache let the query recurse through coroutine new suggestion format with extracted variable name fine-tune the drop span and messages bugfix on runtime borrows tweak message wording filter out ecosystem types earlier apply suggestions clippy check lint level at session level further restrict applicability of the lint translate bid into nop for stable mir detect cycle in type structure