Replace state_for_location with DataflowResultsCursor#64532
Replace state_for_location with DataflowResultsCursor#64532bors merged 3 commits intorust-lang:masterfrom
state_for_location with DataflowResultsCursor#64532Conversation
|
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Use the new dataflow cursor.
DataflowResultsCursorstate_for_location with DataflowResultsCursor
|
This change looks good to me. I had a brief desire to attempt to find out if any open PR's are using |
|
#64207 is exporting most of |
|
The author of #64207 has already changed their clippy PR to use the cursor. |
|
📌 Commit 73c7a68 has been approved by |
… r=tmandry Replace `state_for_location` with `DataflowResultsCursor` These are two different ways of getting the same data from the result of a dataflow analysis. However, `state_for_location` goes quadratic if you try to call it for every statement in the body.
Rollup of 5 pull requests Successful merges: - #64207 (Make rustc_mir::dataflow module pub (for clippy)) - #64348 (PR: documentation spin loop hint) - #64532 (Replace `state_for_location` with `DataflowResultsCursor`) - #64578 (Fix issue22656 with LLDB 8) - #64580 (Update books) Failed merges: r? @ghost
These are two different ways of getting the same data from the result of a dataflow analysis. However,
state_for_locationgoes quadratic if you try to call it for every statement in the body.