Implement once, memoize, and pipe

Problem

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

JavaScript began as a small browser scripting language, then accumulated object, functional, metaprogramming, module, and runtime capabilities while preserving early coercion rules.

Concept explanation

Implement once, memoize, and pipe belongs to “Functions carry environments”. implement once, memoize, and pipe ships as one thin, inspectable slice of a dependency-free functional utility bench.

For implement once, memoize, and pipe, trace concrete input, state transition, output, and failure through a JavaScript semantic rule observable through values, property operations, scope, calls, or protocol steps.

Execution evaluates expressions against lexical environments. Objects are property tables linked through prototypes; functions are callable objects with closures. 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.mjs. Focus: Add implement once, memoize, and pipe to a dependency-free functional utility bench; demo it with: Build counter closure, once, memoize, and pipe without dependencies.

1. Run: node lab.mjs
2. Save baseline evidence. Use property descriptors, scope panels, call stacks, console probes, and deliberately tiny cases.
3. Boundary case: Document and test shipped slice under: Create two counters and prove isolated captured state.
4. Failure case: Add recovery behavior and a regression check for: Retain large object accidentally and find closure ownership.

RESULT
Fresh clone or blank directory can run documented slice and reproduce: Calls show deterministic isolated state; helper contracts and retention path are observable. Starter-level baseline: Two labeled records print in stable order; each exposes value, runtime type, and string representation.

Starter material

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

const cases = [
  { label: "baseline", input: 0 },
  { label: "boundary", input: 1 },
];

function observe(value) {
  // Change only this function while investigating implement once, memoize, and pipe.
  return { value, type: typeof value, text: String(value) };
}

for (const test of cases) console.log(test.label, observe(test.input));

STOP / CLEANUPScripts exit by themselves; no cleanup command required.

Independent exercise

Make it recoverable: implement once, memoize, and pipe

1. Create second case from blank file: Document and test shipped slice under: Create two counters and prove isolated captured state.
2. Then create controlled failure: Add recovery behavior and a regression check for: Retain large object accidentally and find closure ownership.
3. Use Chromium Sources · console · hx · Node REPL to prove behavior, then repair controlled failure.
4. Compare result against supplied acceptance checks and reference approach before marking complete.

Expected result

• Fresh clone or blank directory can run documented slice and reproduce: Calls show deterministic isolated state; helper contracts and retention path are observable.
• Two labeled records print in stable order; each exposes value, runtime type, and string representation.
• Controlled implement once, memoize, and pipe failure produces captured evidence; repair restores stated invariant without hiding error.

Hints

Solution

Attempt both exercises before opening reference approach.