Type a recursive call-initialized object literal property lazily - #64426

Fixes #64420

This patch was written with Claude Code (Opus 5.5), porting Colin McDonnell (@colinhacks)' commit 5c29a1a from #64248 onto the architecture from #64311. I've read it, understand it, and will be the one handling review.

Analysis

After #64311, this works:

const G = object({ name: string(), get children() { return array(G); } });

This, the shape Zod documents with z.lazy, doesn't:

const L = object({ name: string(), children: lazy(() => array(L)) });
// TS7022: 'L' implicitly has type 'any' ...
// TS7024: Function implicitly has return type 'any' ...

checkObjectLiteral types every property assignment eagerly; only accessors go through checkNodeDeferred and get typed later through their own symbol. Typing children means resolving lazy(...), which infers the arrow's return type, which reads L while L's type is still being resolved. The circularity is reported before #64311's recursive-call handling ever gets involved.

Fix

If a property assignment's initializer is a call or new expression, and a function body somewhere inside it refers to a symbol whose type is currently being resolved (per typeResolutions), the property is treated like an accessor: checkObjectLiteral adds it to the literal by its declaration symbol and defers it with checkNodeDeferred, and its type comes from getTypeOfSymbol when something asks for it. Two guards keep it lazy:

• getWidenedProperty leaves it alone, as it does for accessors.
• getTypeOfConcretePropertyOfContextualType returns no contextual type for it while its type is unresolved, since the only type on offer is the literal's own inferred type.

When that deferred type is eventually resolved and re-enters the outer object(...) call, #64311 skips the constraint checks on the recursive resolution, so the cycle ends. The outermost call still checks constraints.

This is 5c29a1a minus the parts of #64248's design that #64311 made unnecessary: the hasObjectLiteralAccessors hook that decided when to defer constraint checks, and the spread-getter check from another commit in that PR. The plain callback-property form (children: () => array(node), 15bb626 in #64248) needs no change; it already infers correctly on main after #64311.

The only shapes this triggers on are a callback that sits inside a call or new expression initializing a property, and that refers to a declaration still being typed. Code that runs immediately is left alone: references outside a function body, inside an immediately invoked function, or in a function's computed name or decorators don't count, matching isUsedInFunctionOrInstanceProperty. Those cases keep their existing errors (covered in the test).

Tests (from #64248, adapted):

• recursiveCallbackArgumentConstraint.ts: direct, nested (array(lazy(...))), chained (lazy(...).optional()), mutual recursion, a context-sensitive callback, errors inside a deferred property, an outer constraint that still fails, an eager reference that still errors, and code that runs immediately (an IIFE, a computed method name) that is still not deferred. Baselines match Infer recursive types through self-referential object literals #64248's except for the intentionally failing strictObject case, which now falls back to the constraint type instead of a partial type with any inside; the error is the same.
• recursiveCallbackArgumentDeclarationEmit.ts: declaration emit of the inferred recursive type.
• hoverThenDiagnosticsRecursiveCallbackArgument_test.go: same diagnostics whether hover or diagnostics run first. I left out Infer recursive types through self-referential object literals #64248's ...WithOutput variants: they fail the same way for the getter form on main (Confusing missing property error in a circular situation #62180, see Restore idempotency to resolveObjectTypeMembers #64372).

No existing baselines change.

Copilot Checklist

I successfully ran the applicable command at the end of my session, and it completed without error:

• npx hereby validate
• npx hereby validate --api (for TypeScript API changes): not applicable

🤖 Generated with Claude Code