dnrops
/
rust
mirror of https://github.com/rust-lang/rust.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Minor improvements in comment for

This commit is contained in:
Gurinder Singh 2024-01-01 13:21:49 +05:30
parent e51e98dde6
commit 884cb41d73
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
compiler/rustc_infer/src/infer/freshen.rs
View File

@ -5,7 +5,7 @@
//! Freshening is used primarily to get a good type for inserting into a cache. The result //! Freshening is used primarily to get a good type for inserting into a cache. The result
//! summarizes what the type inferencer knows "so far". The primary place it is used right now is //! summarizes what the type inferencer knows "so far". The primary place it is used right now is
//! in the trait matching algorithm, which needs to be able to cache whether an `impl` self type //! in the trait matching algorithm, which needs to be able to cache whether an `impl` self type
//! matches some other type X -- *without* affecting `X`. That means if that if the type `X` is in //! matches some other type X -- *without* affecting `X`. That means that if the type `X` is in
//! fact an unbound type variable, we want the match to be regarded as ambiguous, because depending //! fact an unbound type variable, we want the match to be regarded as ambiguous, because depending
//! on what type that type variable is ultimately assigned, the match may or may not succeed. //! on what type that type variable is ultimately assigned, the match may or may not succeed.
//! //!
@ -21,7 +21,7 @@
//! Because of the manipulation required to handle closures, doing arbitrary operations on //! Because of the manipulation required to handle closures, doing arbitrary operations on
//! freshened types is not recommended. However, in addition to doing equality/hash //! freshened types is not recommended. However, in addition to doing equality/hash
//! comparisons (for caching), it is possible to do a `ty::_match` operation between //! comparisons (for caching), it is possible to do a `ty::_match` operation between
//! 2 freshened types - this works even with the closure encoding. //! two freshened types - this works even with the closure encoding.
//! //!
//! __An important detail concerning regions.__ The freshener also replaces *all* free regions with //! __An important detail concerning regions.__ The freshener also replaces *all* free regions with
//! 'erased. The reason behind this is that, in general, we do not take region relationships into //! 'erased. The reason behind this is that, in general, we do not take region relationships into