diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2025-07-07 19:45:41 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-07 19:45:41 +0800 |
| commit | eed55947accb36fdd2af438aa599804aac7dd96b (patch) | |
| tree | 737ae2add9d1a120ac98dcfc30842b483a1f73d8 /compiler/rustc_codegen_llvm/src/context.rs | |
| parent | 02aa4ff12f09f8902b720ab7fc68d5ecfb84dda7 (diff) | |
| parent | 777516652887e3bdfb827bd9d1e83d442266adb1 (diff) | |
| download | rust-eed55947accb36fdd2af438aa599804aac7dd96b.tar.gz rust-eed55947accb36fdd2af438aa599804aac7dd96b.zip | |
Rollup merge of #143528 - RalfJung:stack-pop-cleanup, r=oli-obk
interpret: rename StackPopCleanup The name `StackPopCleanup` stopped making sense a long time ago IMO -- in the common case, it has nothing to do with "cleanup", and everything with where the program should jump next. If we didn't have unwinding this would be just the return block, but given that we do have unwinding I figured maybe "continuation" would be a good name. This comes up in [continuation-passing style](https://en.wikipedia.org/wiki/Continuation-passing_style) and refers to where the program will *continue* when a function is done. So from a PL perspective it is the most fitting term I think -- but it may be too jargony. r? `@oli-obk` what do you think?
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/context.rs')
0 files changed, 0 insertions, 0 deletions