Skip to content

[SE-0343] Fix typo #2812

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

Merged
merged 1 commit into from
Apr 28, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion proposals/0343-top-level-concurrency.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ semantic changes, potentially breaking scripts that already exist.

The solutions will only apply when the top-level code is an asynchronous
context. As a synchronous context, the behavior of top-level code does not
change. In order trigger making the top-level context an asynchronous context, I
change. In order to trigger making the top-level context an asynchronous context, I
propose using the presence of an `await` in one of the top-level expressions.

An await nested within a function declaration or a closure will not trigger the
Expand Down