-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support ES2015 Promise #160
Comments
+1 would love to see this happen. 😃 |
Just discovered the |
@gbrail are you planning to merge the remaining of this branch somewhere in the future? I see a lot of the changes in this branch have already made it into master, which the major exception of the actual Promises implementation |
It's still coming. Rhino is occupying a lot more of my time and it's still
more than I have right now. There are a few outstanding things in another
branch I have that changes NativeError, and then once that's done I'll
merge this, probably next week.
…On Tue, Jun 1, 2021 at 5:44 AM Paul Bakker ***@***.***> wrote:
@gbrail <https://github.com/gbrail> are you planning to merge the
remaining of this branch somewhere in the future? I see a lot of the
changes in this branch have already made it into master, which the major
exception of the actual Promises implementation
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#160 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD7I25CYENIKFNNWCGH3P3TQTI3FANCNFSM4A5RT4BQ>
.
|
So pretty close, great! Have you given async/await any thought? |
Has any thought been given to debugging Promises? As these introduce the async programming model more prominently in Rhino, I wonder what support there'll be for debugging async 'callstacks'. Platforms like Chrome/V8/Node support async debugging and async stacktraces for example |
@gbrail am wondering if we need followup cases for the following things:
|
Yes, I think that if we have comments in PRs from things that we already merged and closed that we should turn them into issues. Thanks for looking at all this! |
V8 has support for the ES6 "Promise" object.
The text was updated successfully, but these errors were encountered: