diff options
| author | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-11-26 15:31:02 +1100 |
|---|---|---|
| committer | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-12-10 12:07:13 +1100 |
| commit | 1d56943f34ee3e1d28ae7677b8410af867f267da (patch) | |
| tree | 2d9fa270f2653d9bcae80c2d0b88a531cdaa8db8 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 119fbd32dc985cf5c0e02f3fa5e02695f4d2fed9 (diff) | |
| download | rust-1d56943f34ee3e1d28ae7677b8410af867f267da.tar.gz rust-1d56943f34ee3e1d28ae7677b8410af867f267da.zip | |
Rename some `Analysis` and `ResultsVisitor` methods.
The words "before" and "after" have an obvious temporal meaning, e.g.
`seek_before_primary_effect`,
`visit_statement_{before,after}_primary_effect`. But "before" is also
used to name the effect that occurs before the primary effect of a
statement/terminator; this is `Effect::Before`. This leads to the
confusing possibility of talking about things happening "before/after
the before event".
This commit removes this awkward overloading of "before" by renaming
`Effect::Before` as `Effect::Early`. It also renames some of the
`Analysis` and `ResultsVisitor` methods to be more consistent.
Here are the before and after names:
- `Effect::{Before,Primary}` -> `Effect::{Early,Primary}`
- `apply_before_statement_effect` -> `apply_early_statement_effect`
- `apply_statement_effect` -> `apply_primary_statement_effect`
- `visit_statement_before_primary_effect` -> `visit_after_early_statement_effect`
- `visit_statement_after_primary_effect` -> `visit_after_primary_statement_effect`
(And s/statement/terminator/ for all the terminator events.)
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
