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

104th Meeting of TC39, notes #349

Merged
merged 6 commits into from
Nov 4, 2024
Merged

104th Meeting of TC39, notes #349

merged 6 commits into from
Nov 4, 2024

Conversation

gesa
Copy link
Member

@gesa gesa commented Oct 25, 2024

Great job with summaries and conclusions everyone. Just a few more to go.

Missing Speaker Summaries and Conclusions:

  • Day 1
  • Day 2
    • @ljharb Error.isError
    • @ben-allen Normative: Allow use of non-ISO 4217 data in CurrencyDigits AO
  • Day 3
    • @syg on js0/jsSugar

@ctcpip
Copy link
Member

ctcpip commented Oct 25, 2024

I'm guessing we probably aren't in the habit of doing this, but we should move continuations to be colocated with the original topics. Otherwise, they may end up sort of lost because people looking at the notes have no indication that the topic continued later and there are more notes.

cc @tc39/chairs

@michaelficarra
Copy link
Member

@ctcpip I'd prefer to leave them in place and have the notes be an accurate recording of events. What do you think about just putting a link to the continuation at the end of any continued topic?

@ctcpip
Copy link
Member

ctcpip commented Nov 1, 2024

@michaelficarra it's not my preference, but would be an acceptable compromise

@gesa gesa marked this pull request as ready for review November 4, 2024 02:19
@gesa
Copy link
Member Author

gesa commented Nov 4, 2024

@tc39/chairs no longer in draft, merge at will.

@ryzokuken ryzokuken changed the title DRAFT: 104th Meeting of TC39, notes 104th Meeting of TC39, notes Nov 4, 2024
@ryzokuken ryzokuken merged commit 38c1ecd into tc39:main Nov 4, 2024
1 check passed
@nicolo-ribaudo
Copy link
Member

Hey, I had gesa#1 that got missed (GitHub gave me a permission error when I tried to push directly to this PR)

@ryzokuken
Copy link
Member

@nicolo-ribaudo can you make a PR to this repo instead?

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

Successfully merging this pull request may close these issues.

9 participants