- From: Takeshi Yoshino <notifications@github.com>
- Date: Fri, 04 Nov 2016 00:32:16 -0700
- To: whatwg/streams <streams@noreply.github.com>
Received on Friday, 4 November 2016 07:33:03 UTC
I also see some good point in Adam's analysis and isonmad's proposal, but am leaning toward the plan to mark the "status" promises as handled. Regarding the lazy promise creation idea, I'd like to confirm if this related to the principle about semantics of getters we discussed during the Fetch API's `Response.body` design. That is IIRC that if evaluating the member has any side-effect observable in JS should be implemented as a method. As showing the warnings is not observable in JS but only inspector, it's ok? -- 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-258362060
Received on Friday, 4 November 2016 07:33:03 UTC