Built-in syntax isn't "in scope" so these OccNames map to wired-in Names with BuiltInSyntax. However, this should only be necessary while resolving names produced by Template Haskell splices since we take care to encode built-in syntax names specially in interface files. See Note [Symbol table representation of names] in GHC.Iface.Binary.

Moreover, there is no need to include names of things that the user can't write (e.g. type representation bindings like $tc(,,,)).

Given a type ty, if ty is not of kind Type, return a data constructor that will box it, and the type of the boxed thing, which does now have kind Type. See Note [Boxing constructors]

Make a *promoted* list.

Make a tuple type. The list of types should not include any RuntimeRep specifications. Boxed 1-tuples are flattened. See Note [One-tuples]

Make a tuple type. The list of types should not include any RuntimeRep specifications. Boxed 1-tuples are *not* flattened. See Note [One-tuples] and Note [Don't flatten tuples from HsSyn] in GHC.Core.Make

Build the type of a small tuple that holds the specified type of thing Flattens 1-tuples. See Note [One-tuples].

Specialization of unboxedTupleSumKind for tuples

Specialization of unboxedTupleSumKind for sums

Replaces constraint tuple names with corresponding boxed ones.

If the given name is that of a constraint tuple, return its arity.

Make a fake, recovery TyCon from an existing one. Used when recovering from errors in type declarations

Type constructor for n-ary unboxed sum.

Data constructor for i-th alternative of a n-ary unboxed sum.

type LiftedRep = 'BoxedRep 'Lifted

type UnliftedRep = 'BoxedRep 'Unlifted

Should this name be considered in-scope, even though it technically isn't?

This ensures that we don't filter out information because, e.g., Data.Kind.Type isn't imported.

See Note [pretendNameIsInScope].