TypedArray validation gets a dedicated witness-record step (
306a770)
The spec now introduces a dedicated operation for validating TypedArray bounds into a witness Record, intended for use by ValidateTypedArray and related steps. This is the most substantive change of the day: it factors validation into a clearer shared abstraction and should make the memory-model-related text easier to follow.
Spec terminology and references are normalized (
294dcc2, 0d9df3c, 2faa8c2)
The day also updates time-related notes to reflect modern ISO 8601 support for 24:00 and the existence of RFC 9557 for time zone names, normalizes RFC links to the canonical rfc-editor.org/info form, and adds an autolinked definition for “expanded year”. These are editorial, but they improve precision and reduce stale or inconsistent references.
Other misc changes
- Use named time constants more consistently, including new nsPerSecond / nsPerMillisecond / nsPerMicrosecond constants (777fc02)
- Clarify that MethodDefinitionEvaluation on object properties does not produce a PrivateElement (
7cb06a7) - Simplify coercion in DoWait (0cdd9cc)
- Clarify IsNoTearConfiguration for bigint types and require SEQ-CST ordering (0f411cc)
- Use a more common alias name in ValidateIntegerTypedArray (05e3c17)
- Refactor ValidateIntegerTypedArray on top of IsNoTearConfiguration (d94d54e)
- Avoid some unions with ~unused~ (2ce6555)