From 9477e32936dbb953fee14d5b26f81cfd93cd7d43 Mon Sep 17 00:00:00 2001 From: Richard Smith Date: Wed, 22 Jul 2026 15:53:30 -0700 Subject: [PATCH] Add explanation of `TypeInstId` to check docs. (#7555) --- toolchain/docs/check/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/toolchain/docs/check/README.md b/toolchain/docs/check/README.md index 6f5dc6f5b01b..d5856e8fd6f8 100644 --- a/toolchain/docs/check/README.md +++ b/toolchain/docs/check/README.md @@ -137,6 +137,9 @@ listed in the `SemIR::IdKind` enumeration defined in - `SemIR::InstId`: Refers to a specific instance of an instruction. For example, this should be used if the operand may have side-effects or a meaningful location. +- `SemIR::TypeInstId`: Refers to a specific instance of an instruction of type + `type`. This should be used instead of `InstId` if you know that the type of + the instruction is always `type` (or the "error" type). - `SemIR::ConstantId`: An abstract reference to a known constant value. This should be used instead of `InstId` if you care only about the identity of the value and not how it was formed.