# Impredicative Guarded Instantiation: Practice Notes

Impredicative Guarded Instantiation shows up often in coding rounds. Here is how I talk through it when the interviewer is watching.

## Key idea

Allow a type variable to be instantiated with a polymorphic type only when a guard (or rigid prenex form) makes the choice unambiguous.

## Steps to say out loud

1. Restate the input and the exact ask, and nail down constraints and overflow.
2. Name the pattern (binary search on the answer, monotonic stack or deque, interval / interval-DP, string hashing, graph traversal, or shortest paths) and why a nested scan or naive search fails.
3. Code it, then trace a short example plus one empty or already-solved edge case.

## Complexity

More programs type-check than predicative HM; inference needs extra care to stay principal.

## Common mistake

Unguarded impredicative instantiation, which can make inference lose principal types or loop.

## Practice tip

Time yourself: two minutes to explain, ten to code, three to test edges. Disclosure: I work on Linkjob AI. I also keep a practice cheat sheet at AI assistant for technical interviews.