Re: [whatwg/streams] Internal promises that can be rejected need to be handled (#468)

By relation I meant the next sentence (catching one doesn't prevent the other from throwing), perhaps a semicolon would've worked better. And yes I realize they're rejected with the same error, that's why its redundant.

Reading through the ES spec I guess I realize I'm just too use to how Promises are implemented in Chrome / in Closure. It doesn't look like its part of the ES spec that unhanded errors should be logged.

You can copy the code below in Chrome and get an error on the first example. However you won't in FireFox.

`Promise.reject(lol error') // causes the error: Uncaught (in promise) lol error in Chrome`
`Promise.reject('lol error').catch(() => {}) // no error in Chrome`

Guess this can be closed since it isn't part of the ES Promise spec. If it was (which I assumed) then I would've had an argument.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/468#issuecomment-227557561