user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Auto merge of #147826 - Muscraft:update-typos, r=Noratrieb

Browse source 
Update typos

I saw that `typos` was a few versions out of date and figured it would be a good idea to update it. Upgrading to `1.38.1` adds the [July](https://github.com/crate-ci/typos/issues/1331), [August](https://github.com/crate-ci/typos/issues/1345), and [September](https://github.com/crate-ci/typos/issues/1370) dictionary updates. As part of this change, I also sorted the configuration file.
This commit is contained in:
bors 2025-10-22 13:11:47 +00:00
commit 4d94478977
27 changed files with 75 additions and 64 deletions
Download patch file Download diff file Expand all files Collapse all files

2
compiler/rustc_next_trait_solver/src/solve/eval_ctxt/mod.rs
View file

@ -980,7 +980,7 @@ where
}
}
/// This sohuld only be used when we're either instantiating a previously
/// This should only be used when we're either instantiating a previously
/// unconstrained "return value" or when we're sure that all aliases in
/// the types are rigid.
#[instrument(level = "trace", skip(self, param_env), ret)]

2
compiler/rustc_next_trait_solver/src/solve/mod.rs
View file

@ -39,7 +39,7 @@ use crate::solve::assembly::Candidate;
///
/// We previously used `cx.recursion_limit().0.checked_ilog2().unwrap_or(0)` for this.
/// However, it feels unlikely that uncreasing the recursion limit by a power of two
/// to get one more itereation is every useful or desirable. We now instead used a constant
/// to get one more iteration is every useful or desirable. We now instead used a constant
/// here. If there ever ends up some use-cases where a bigger number of fixpoint iterations
/// is required, we can add a new attribute for that or revert this to be dependant on the
/// recursion limit again. However, this feels very unlikely.