Rollup merge of #105681 - tshepang:doc-mir-visit, r=Nilstrieb
some fixes/improvements to mir::visit module
This commit is contained in:
commit
da07053ee1
@ -3,15 +3,15 @@
|
||||
//! ## Overview
|
||||
//!
|
||||
//! There are two visitors, one for immutable and one for mutable references,
|
||||
//! but both are generated by the following macro. The code is written according
|
||||
//! to the following conventions:
|
||||
//! but both are generated by the `make_mir_visitor` macro.
|
||||
//! The code is written according to the following conventions:
|
||||
//!
|
||||
//! - introduce a `visit_foo` and a `super_foo` method for every MIR type
|
||||
//! - `visit_foo`, by default, calls `super_foo`
|
||||
//! - `super_foo`, by default, destructures the `foo` and calls `visit_foo`
|
||||
//!
|
||||
//! This allows you as a user to override `visit_foo` for types are
|
||||
//! interested in, and invoke (within that method) call
|
||||
//! This allows you to override `visit_foo` for types you are
|
||||
//! interested in, and invoke (within that method call)
|
||||
//! `self.super_foo` to get the default behavior. Just as in an OO
|
||||
//! language, you should never call `super` methods ordinarily except
|
||||
//! in that circumstance.
|
||||
|
Loading…
Reference in New Issue
Block a user