Open jridgewell opened 1 year ago
_Prototype pollution mitigation / Symbol.proto for Stage 1 (slides)_ reaches Stage 1
Symbol as WeakMap key for Stage 4 (spec) reaches Stage 4
Change Array by copy for Stage 4 (spec) reaches Stage 4
_Intl.NumberFormat V3 for Stage 4 (spec, slides)_ reaches Stage 4
Intl.DurationFormat Stage 3 update (Slides TBW) has consensus
Explicit Resource Management Stage 3 update (slides, spec) gets consensus on:
await
as Identifier in using
using
in top level of eval
Discuss SuppressedError argument overlap: error
and cause
(issue) gets consensus to remove cause
from a SuppressedError
Intl Locale Info API Stage 3 update ([Slides](https://docs.google.com/presentation/d/1L-IRdBeLaOrnj-EFmUWxB_ALe9TMvzy4IajuWTg1E), spec) got consensus on things but the conclusion notes aren't written yet…
Looks like they chose to add get
prefixes: https://github.com/tc39/proposal-intl-locale-info/pull/67 has been merged.
Async Contexts for Stage 1 (slides) reaches Stage 1
ArrayBuffer transfer for Stage 3 (slides, spec) reaches Stage 3
Intl era and monthCode for Stage 2 (slides, spec) reaches Stage 2
Temporal Stage 3 update and normative PRs (slides, spec) got consensus on everything except https://github.com/tc39/proposal-temporal/pull/2479
Symbol Predicates for stage 2 reaches Stage 2 with static methods
_Async Explicit Resource Management for Stage 3? (slides, spec)_ reaches Stage 3, but the using await
and async using
syntax discussion is still ongoing (and will be resolved by the next meeting)
in other words, it's not at stage 3 yet, but it will become so once the one outstanding issue is resolved.
getIntrinsic, with an iterator for stage 2 remains at Stage 1, concerns about memory problems being pushed into the engine
_Problems with import assertions for module types and a possible general solution + downgrade to Stage 2 (HTML issue, slides, slides for continuation)_ relegates Import Assertions to Stage 2, but we're relaxing the host evaluation restriction. We'll reconsider syntax and semantics to solve the Web's usecase.
Decorator context.access
object API (issue) gets consensus on both points
What about JSON
discussion?
_JSON.parse source text access Stage 3 update (slides, spec)_ got consensus to merge #35 and #39, expect to advance next meeting.
- Both valid before and after the export keyword, but exclusively before or after
Does this mean we can no longer add export
decorators in future extensions?
That seems like a sad choice?
https://github.com/tc39/agendas/blob/main/2023/01.md