Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jan 2023 #86

Open
jridgewell opened this issue Jan 30, 2023 · 24 comments
Open

Jan 2023 #86

jridgewell opened this issue Jan 30, 2023 · 24 comments

Comments

@jridgewell
Copy link
Member

https://github.com/tc39/agendas/blob/main/2023/01.md

@jridgewell
Copy link
Member Author

Prototype pollution mitigation / Symbol.proto for Stage 1 (slides) reaches Stage 1

@jridgewell
Copy link
Member Author

Symbol as WeakMap key for Stage 4 (spec) reaches Stage 4

@jridgewell
Copy link
Member Author

Change Array by copy for Stage 4 (spec) reaches Stage 4

@jridgewell
Copy link
Member Author

Intl.NumberFormat V3 for Stage 4 (spec, slides) reaches Stage 4

@jridgewell
Copy link
Member Author

Intl.DurationFormat Stage 3 update (Slides TBW) has consensus

@jridgewell
Copy link
Member Author

Explicit Resource Management Stage 3 update (slides, spec) gets consensus on:

  • Ban await as Identifier in using
  • Ban using in top level of eval

@jridgewell
Copy link
Member Author

jridgewell commented Jan 31, 2023

Discuss SuppressedError argument overlap: error and cause (issue) gets consensus to remove cause from a SuppressedError

@jridgewell
Copy link
Member Author

Intl Locale Info API Stage 3 update (Slides, spec) got consensus on things but the conclusion notes aren't written yet…

@ehoogeveen-medweb
Copy link

Looks like they chose to add get prefixes: tc39/proposal-intl-locale-info#67 has been merged.

@jridgewell
Copy link
Member Author

Parallel async iterators via a tweak to iterator helpers (slides, proposal) reaches consensus:

  • Sync iterators remain at Stage 3
  • Async iterators are split and relegated to Stage 2 to discuss parallelism

@jridgewell
Copy link
Member Author

Async Contexts for Stage 1 (slides) reaches Stage 1

@jridgewell
Copy link
Member Author

ArrayBuffer transfer for Stage 3 (slides, spec) reaches Stage 3

@jridgewell
Copy link
Member Author

Intl era and monthCode for Stage 2 (slides, spec) reaches Stage 2

@jridgewell
Copy link
Member Author

Temporal Stage 3 update and normative PRs (slides, spec) got consensus on everything except tc39/proposal-temporal#2479

@jridgewell
Copy link
Member Author

Symbol Predicates for stage 2 reaches Stage 2 with static methods

@jridgewell
Copy link
Member Author

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)

@ljharb
Copy link
Member

ljharb commented Feb 1, 2023

in other words, it's not at stage 3 yet, but it will become so once the one outstanding issue is resolved.

@jridgewell
Copy link
Member Author

getIntrinsic, with an iterator for stage 2 remains at Stage 1, concerns about memory problems being pushed into the engine

@jridgewell
Copy link
Member Author

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.

@jridgewell
Copy link
Member Author

Decorator context.access object API (issue) gets consensus on both points

@jridgewell
Copy link
Member Author

jridgewell commented Feb 2, 2023

Decorators and export Ordering (issue, slides) achieves consensus on:

  • Both valid before and after the export keyword, but exclusively before or after
  • toString will not include decorators before, it's cut off at the export keyword

@zloirock
Copy link
Member

zloirock commented Feb 3, 2023

What about JSON discussion?

@jridgewell
Copy link
Member Author

JSON.parse source text access Stage 3 update (slides, spec) got consensus to merge #35 and #39, expect to advance next meeting.

@trusktr
Copy link

trusktr commented Mar 12, 2023

  • 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants