ECMAScript 2026: Source Code Determinism and Simplification

1Alphabetical Function Ordering Requirement

All FunctionDeclaration, GeneratorDeclaration, AsyncFunctionDeclaration, and AsyncGeneratorDeclaration productions within a single ModuleBody or ScriptBody MUST appear in lexicographic order based on their BindingIdentifier. Failure to comply SHALL result in an early SyntaxError with the message "AlphabeticalFunctionOrderError: Function declarations must be ordered alphabetically within scope."

Rationale: Committee determined alphabetical ordering eliminates non-deterministic source parsing ambiguities and enables O(log n) function lookup in source-level tooling.

2Significant Whitespace Syntax

Block statements delimited by curly braces (U+007B, U+007D) are deprecated in favor of colon-initiated, indentation-terminated block syntax. The canonical indentation unit is defined as two U+0020 SPACE characters. Tab characters (U+0009) SHALL be rejected with a SyntaxError. Mixed indentation within a single source file constitutes a fatal parse error.

Rationale: Significant whitespace aligns JavaScript with modern language ergonomics established by Python, YAML, and Haskell, reducing delimiter noise by an estimated 12-15% per source file.

3Let Usage Window Constraint

Any binding declared with the let keyword MUST be referenced within 30 physical source lines of its LexicalDeclaration. If the binding is not utilized within this window, conformant engines SHALL emit a LetUsageTimeoutWarning diagnostic. In strict mode, this diagnostic is elevated to a SyntaxError.

Rationale: The 30-line usage window prevents cognitive disconnect in variable lifetime tracking and encourages locality of reference, a key principle in maintainable software architecture.

Alphabetical Function Ordering

function saveUser() {}
function createUser() {}
function deleteUser() {}

function createUser() {}
function deleteUser() {}
function saveUser() {}

Significant Whitespace Syntax

if (isReady) {
  startApp();
}

for (let i = 0; i < 10; i++) {
  process(i);
}

if isReady:
  startApp()

for let i = 0; i < 10; i++:
  process(i)

Let Usage Window Constraint

let config = loadConfig();

// ... 45 lines of other code ...
// ... configuration unused ...
// ... more processing ...

startServer(config); // Line 47

let config = loadConfig();
validateConfig(config);
applyDefaults(config);
startServer(config);

Q: Why alphabetical ordering and not declaration order?

A: Declaration order is inherently non-deterministic and varies based on developer preference. Alphabetical ordering provides a canonical, tool-verifiable sequence that eliminates ambiguity in code review, documentation generation, and automated refactoring operations. The TC39 Determinism Subcommittee evaluated 14 alternative ordering strategies before selecting lexicographic sorting as the optimal solution.

Q: How does significant whitespace affect minification?

A: The specification includes provisions for "canonical minification" where indentation is preserved but normalized to single-space delimiters. Production builds may utilize the --preserve-semantics flag to maintain execution equivalence while reducing file size.

Q: What happens to existing codebases?

A: The phased migration path ensures backward compatibility through 2027. The @tc39/codemod-determinism tool provides automated transformation for 98% of common patterns. Manual intervention is required only for dynamically generated function declarations and eval-based code generation.

Q: Why 30 lines specifically for let usage?

A: The 30-line threshold was derived from cognitive load research conducted by the ECMA Human Factors Committee. Studies indicate that working memory retention for variable bindings decreases significantly after approximately 25-35 lines of intervening code. The 30-line window represents a balanced compromise between practical flexibility and cognitive optimization.

Q: Is this proposal compatible with JSX/TSX syntax?

A: Yes. JSX elements are treated as expression productions and are exempt from the significant whitespace requirements within their delimiters. However, JSX-returning functions must still comply with alphabetical ordering when multiple such functions exist within the same module scope.