diff options
| author | bors <bors@rust-lang.org> | 2022-08-09 11:05:42 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-08-09 11:05:42 +0000 |
| commit | cc4dd6fc9f1a5c798df269933c7e442b79661a86 (patch) | |
| tree | a840aa633ef8e3443f86d21e239432139e2a4f3f /library/std/src/sys/unix/alloc.rs | |
| parent | 5af97e8b0b9649ed14b0b4528a610ff841b6365e (diff) | |
| parent | 7547084ff673dcfdb2c6bcf7dc7a81190513ed40 (diff) | |
| download | rust-cc4dd6fc9f1a5c798df269933c7e442b79661a86.tar.gz rust-cc4dd6fc9f1a5c798df269933c7e442b79661a86.zip | |
Auto merge of #100089 - JakobDegen:no-invalidate-visitor, r=tmiasko
Add option to `mir::MutVisitor` to not invalidate CFG. This also applies that option to some uses of the visitor. I had considered a design more similar to #100087 in which we detect if the CFG needs to be invalidated, but that is more difficult with the visitor API and so I decided against it. Another alternative to this design is to offer an API for "saving" and "restoring" CFG caches across arbitrary code. Such an API is more general, and so we may eventually want it anyway, but it seems overkill for this use case. r? `@tmiasko`
Diffstat (limited to 'library/std/src/sys/unix/alloc.rs')
0 files changed, 0 insertions, 0 deletions