Constraints

Problem

What becomes confusing, fragile, or impossible without understanding constraints? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

TypeScript added gradual static analysis to JavaScript without replacing its runtime, preserving ecosystem compatibility through erasure.

Concept explanation

Constraints belongs to “Generics express relationships”. Generics express relationships among inputs and outputs; useful constraints preserve inference. This lesson turns constraints into a working part of weekly fixture.

For constraints, trace concrete input, state transition, output, and failure through a compile-time relationship that constrains JavaScript while leaving runtime values and external data untrusted.

Types constrain possible programs during analysis, then disappear. Runtime values remain JavaScript values and external data remains untrusted. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Worked example

Start from supplied lab.ts. Focus: Build constraints around this exact fixture: Implement typed groupBy/get/collection transform with keyof constraint.

1. Run: npx tsc --strict --noEmit lab.ts
2. Save baseline evidence. Read inferred types, diagnostics, emitted JavaScript, declarations, module traces, and source maps.
3. Boundary case: Add constraints support for weekly boundary case: Compare inference with explicit and needless type parameters.
4. Failure case: Make constraints surface—not hide—this failure: Permit unrelated output type and show unsound assertion, then remove it.

RESULT
constraints handles baseline and boundary while preserving this observable result: Call sites infer precise types; invalid key fails compile; no assertion hides relationship. Starter-level baseline: Strict type checking exits successfully. Changing result.value to a string-only operation produces a compiler diagnostic.

Starter material

Create lab.ts, paste this exact content, then run the command below.

type Observation<T> = { topic: string; value: T; valid: boolean };

function observe<T>(topic: string, value: T): Observation<T> {
  return { topic, value, valid: value !== undefined };
}

const result = observe("constraints", 1);
console.log(result.value);

STOP / CLEANUPCompiler exits by itself; no cleanup command required.

Independent exercise

Add one real case: constraints

1. Create second case from blank file: Add constraints support for weekly boundary case: Compare inference with explicit and needless type parameters.
2. Then create controlled failure: Make constraints surface—not hide—this failure: Permit unrelated output type and show unsound assertion, then remove it.
3. Use tsc · hx LSP · emitted JS · source maps to prove behavior, then repair controlled failure.
4. Compare result against supplied acceptance checks and reference approach before marking complete.

Expected result

• constraints handles baseline and boundary while preserving this observable result: Call sites infer precise types; invalid key fails compile; no assertion hides relationship.
• Strict type checking exits successfully. Changing result.value to a string-only operation produces a compiler diagnostic.
• Controlled constraints failure produces captured evidence; repair restores stated invariant without hiding error.

Hints

Solution

Attempt both exercises before opening reference approach.