diff options
| author | bors <bors@rust-lang.org> | 2022-10-19 06:53:31 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-10-19 06:53:31 +0000 |
| commit | 314ff050156cc8f5cb60a13e5d26966257245a22 (patch) | |
| tree | 7ae86746fdfa2abcde456352bd6d946eca4996eb /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 1c294d1de2ce2d884191451064bda46952cfb87b (diff) | |
| parent | 2420d533f2cba3d940fe4ed9f04bfeb1a51bc689 (diff) | |
| download | rust-314ff050156cc8f5cb60a13e5d26966257245a22.tar.gz rust-314ff050156cc8f5cb60a13e5d26966257245a22.zip | |
Auto merge of #2322 - saethlin:stack-inspection-tools, r=oli-obk
Ideas on getting information about borrow stacks during execution From time to time people ask what some borrow stack looks like in some code. I just know that I am terrible at doing Stacked Borrows by hand, so I always toss together something like this. I know that Miri has logging, but I've never found it particularly useful because there's just too much output. Also I personally don't think about exactly what the state of a borrow stack is, but this seems to be something that newcomers to Stacked Borrows always want. Update: This has been sitting as S-waiting-on-author for a long time. I bring it out from time to time to explain Stacked Borrows to people, and just now `@JakobDegen` said > Can we please merge that btw? It's such a valuable teaching tool > Interfaces can be fixed later I'm inclined to trust Jake's judgement here.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions