Skip to content

RegExp Symbol method protocol: observable property access ordering #609

@frostney

Description

@frostney

Summary

Make RegExp Symbol methods follow the spec's observable property access ordering.

Why

83 test262 tests fail because Symbol methods read properties in the wrong order, skip ToLength on lastIndex, and miss constructor[Symbol.species] dispatch.

Current behavior

Symbol methods read internal properties directly without spec-ordered Get/Set operations.

Expected behavior

Property accesses follow ES2026 §22.2.6.* step order exactly.

Scope notes

  • Source: Goccia.Builtins.GlobalRegExp.pas
  • Not a regex engine issue — runtime protocol behavior
  • 35 Symbol.replace, 16 Symbol.match, 16 Symbol.split, 8 Symbol.search, 8 Symbol.matchAll

Metadata

Metadata

Assignees

No one assigned

    Labels

    engineTGocciaEngine: language semantics, ECMAScript built-ins, parser, interpreter, bytecode VMspec complianceMismatch against official JavaScript/TypeScript specification

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions