diff options
| author | Youngsuk Kim <joseph942010@gmail.com> | 2020-06-21 11:43:30 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-21 11:43:30 -0400 |
| commit | 893077ca76eeb1ad35608872d534478d68c953c9 (patch) | |
| tree | d6eb694b26f8365d158b6578e1e24eae59c7f1ba | |
| parent | 63740548aa8887c92d8976ccf478cfb0c44611a5 (diff) | |
| download | rust-893077ca76eeb1ad35608872d534478d68c953c9.tar.gz rust-893077ca76eeb1ad35608872d534478d68c953c9.zip | |
Update src/librustc_mir/monomorphize/collector.rs
typo fix Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
| -rw-r--r-- | src/librustc_mir/monomorphize/collector.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/librustc_mir/monomorphize/collector.rs b/src/librustc_mir/monomorphize/collector.rs index 448d8cdd6c6..e51d9ba9c02 100644 --- a/src/librustc_mir/monomorphize/collector.rs +++ b/src/librustc_mir/monomorphize/collector.rs @@ -79,7 +79,7 @@ //! function or method call (represented by a CALL terminator in MIR). But //! calls are not the only thing that might introduce a reference between two //! function mono items, and as we will see below, they are just a -//! specialized of the form described next, and consequently will not get any +//! specialization of the form described next, and consequently will not get any //! special treatment in the algorithm. //! //! #### Taking a reference to a function or method |