Re: [whatwg/streams] Marking promise rejections as handled (#547)

Is your idea to run the suppression (either `thenPromise` or `[[PromiseIsHandled]]`) on `releaseLock()` call (maybe right before rejecting them), or to mark promises considered to be "state promises" from the beginning?

I think if the needs for marking promise rejections (or fulfillment) handled are considered to be common, we should address this as you said in the OP here than use of ad-hoc suppression (no-op) as you introduced in the Chromium bug tracker.

Can we come up with clear and reasonable criteria (guideline) for deciding whether or not to use this? The phrase "state promises" looks to be capturing the scope well, but still sounds a bit vague.

If we focus only on this issue specifically, it looks we should just mark promises that became (on releaseLock()) to be not expected to be handled as far as the code is "correct" (after releaseLock(), we shouldn't need to touch the promises basically).

-- 
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/547#issuecomment-254866758