- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 12 Feb 2019 11:05:30 -0800
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 12 February 2019 19:05:56 UTC
It seems like using https://tc39.github.io/ecma262/#sec-createresolvingfunctions (and then adding a [[Promise]] field to the result) would work, although I'm a bit unsure about the consequences of a promise floating around with multiple resolve/reject functions associated with it (one from user code and one from the UA). Ideally UA code should not be resolving/rejecting user-provided promises. So maybe there is a better structure than the one I outlined above, hmm. For example, [[Resolve]] and [[Reject]] could be null for user-provided promises, and the first steps of "resolve a promise"/"reject a promise" could assert they are non-null, i.e. assert that the promise was UA-created and not user-created? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/issues/490#issuecomment-462891189
Received on Tuesday, 12 February 2019 19:05:56 UTC