From 3d59d4f51179d0562f56c779edbf2a258ef6b26e Mon Sep 17 00:00:00 2001 From: Veera <sveera.2001@gmail.com> Date: Mon, 9 Sep 2024 22:38:59 -0400 Subject: [PATCH] Fix Typo and Remove Outdated Line About C Variadics This PR does two minor fixes: 1. Removes the line "c-variadic functions are declared with at least one named argument" since it is no longer true since 124048 got merged. 2. Fixes typo: "lingint" -> "linting". --- src/ast-validation.md | 1 - src/mir/passes.md | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/src/ast-validation.md b/src/ast-validation.md index 9a5d13d52..fa0f1d954 100644 --- a/src/ast-validation.md +++ b/src/ast-validation.md @@ -26,7 +26,6 @@ example, when visiting a function declaration, `AstValidator` checks that the function has: * no more than `u16::MAX` parameters; -* c-variadic functions are declared with at least one named argument; * c-variadic argument goes the last in the declaration; * documentation comments aren't applied to function parameters; * and other validations. diff --git a/src/mir/passes.md b/src/mir/passes.md index d182b3fb5..b15590699 100644 --- a/src/mir/passes.md +++ b/src/mir/passes.md @@ -31,7 +31,7 @@ where we can access the MIR dialect for type checking or other purposes: ## Implementing and registering a pass A `MirPass` is some bit of code that processes the MIR, typically transforming it along the way -somehow. But it may also do other things like lingint (e.g., [`CheckPackedRef`][lint1], +somehow. But it may also do other things like linting (e.g., [`CheckPackedRef`][lint1], [`CheckConstItemMutation`][lint2], [`FunctionItemReferences`][lint3], which implement `MirLint`) or optimization (e.g., [`SimplifyCfg`][opt1], [`RemoveUnneededDrops`][opt2]). While most MIR passes are defined in the [`rustc_mir_transform`][mirtransform] crate, the `MirPass` trait itself is