-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Revert: repl: support top-level await #17807
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'm +1 on this but I would also be plus one on keeping the new functionality as experimental and keeping it behind a flag while the issues are worked through. Top level await is quite popular and users want it. |
Yes, I'm definitely in favor of having top level await. I put this together to give us one option. |
Commit logs need more context. I, for one, have no idea why it's being reverted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-1 from me because of #15566 (comment). I’d rather see it being hidden behind a flag, an approach okay with @bmeck in #15566 (comment).
I’m ok for a flag too. |
A flag it is then! |
PR-URL: #19604 Refs: #17807 Refs: #15566 (comment) Reviewed-By: Gus Caplan <me@gus.host>
PR-URL: #19604 Refs: #17807 Refs: #15566 (comment) Reviewed-By: Gus Caplan <me@gus.host>
This reverts #15566
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
deps, test, repl