domenic/promises-unwrapping issues and pull requests

#100 - Fulfilled vs. Resolved

Issue - State: closed - Opened by bterlson over 10 years ago - 5 comments
Labels: question

#99 - Implement January consensus: simplify resolution

Issue - State: closed - Opened by domenic over 10 years ago - 7 comments
Labels: normative-change, abstract-underpinnings

#98 - Implement January consensus: remove Promise.cast

Issue - State: closed - Opened by domenic over 10 years ago - 1 comment
Labels: normative-change, es-manifestation

#97 - thisArgument of new Promise resolver can be more useful

Issue - State: closed - Opened by smcmurray over 10 years ago - 2 comments
Labels: question

#96 - Update with "This proposal has progressed to the Draft ECMAScript 6 Specification..."

Issue - State: closed - Opened by rwaldron over 10 years ago - 2 comments

#95 - Allow constructors to return new objects.

Issue - State: open - Opened by cscott almost 11 years ago - 7 comments
Labels: question

#94 - Potential inconsistency in using [[PromiseConstructor]] in Promise Resolution Handler

Issue - State: open - Opened by domenic almost 11 years ago - 6 comments
Labels: normative-change, subclassing

#93 - Add Promise.fromGenerator

Issue - State: closed - Opened by cscott almost 11 years ago - 3 comments

#92 - Throw error if Promise.all counter exceeds Number.MAX_SAFE_INTEGER?

Issue - State: closed - Opened by anba almost 11 years ago - 8 comments
Labels: question

#91 - Update to align with ES6 spec text

Issue - State: closed - Opened by domenic almost 11 years ago - 7 comments
Labels: make-like-es-spec

#90 - What happens if ArrayCreate throws in Promise.all?

Issue - State: closed - Opened by bzbarsky almost 11 years ago - 8 comments
Labels: invalid

#89 - CountdownHolder setup is not robust in the face of broken promises

Issue - State: closed - Opened by bzbarsky almost 11 years ago - 8 comments
Labels: bug, normative-change

#88 - Promise constructor: Handing of synchronous of resolver exceptions

Issue - State: closed - Opened by allenwb almost 11 years ago - 11 comments
Labels: question

#87 - Spec creates strict requirements on subclass constructors

Issue - State: open - Opened by sicking almost 11 years ago - 55 comments
Labels: question

#86 - Explain use of `Promise.cast`

Issue - State: closed - Opened by domenic almost 11 years ago - 1 comment
Labels: editorial

#85 - [Guide] creating a promise and continue to run steps async

Issue - State: closed - Opened by marcoscaceres almost 11 years ago - 14 comments

#84 - [guide] Rejections Should Be Errors should cater for DOMException

Issue - State: closed - Opened by marcoscaceres almost 11 years ago - 9 comments

#83 - Reentrancy issues in Deferred Construction Functions

Issue - State: closed - Opened by anba almost 11 years ago - 1 comment
Labels: bug

#82 - ExecutePromiseReaction assumes all Callables have a [[Realm]] internal slot

Issue - State: closed - Opened by anba almost 11 years ago - 8 comments
Labels: bug

#81 - Missing completion values

Issue - State: closed - Opened by anba almost 11 years ago - 2 comments
Labels: editorial

#80 - Promise.deferred()?

Issue - State: closed - Opened by juandopazo almost 11 years ago - 20 comments
Labels: question

#79 - Thenable coercion weak map logic is still not quite right

Issue - State: closed - Opened by domenic almost 11 years ago - 8 comments
Labels: normative-change, abstract-underpinnings, question

#78 - Promise Reaction Functions and Promise Resolution Handler Functions don't need to be real functions

Issue - State: closed - Opened by domenic almost 11 years ago - 5 comments
Labels: abstract-underpinnings, editorial

#77 - Thenable coercion should use thenable.then(deferred.resolve, deferred.reject), not deferred.resolve(thenable)

Issue - State: closed - Opened by rossberg almost 11 years ago - 4 comments
Labels: bug, normative-change

#76 - Terminology: overuse of "resolv*"

Issue - State: closed - Opened by allenwb almost 11 years ago - 8 comments
Labels: editorial

#75 - Promise.race with empty lists

Issue - State: closed - Opened by juandopazo about 11 years ago - 18 comments
Labels: question

#74 - Remove `Invoke` usage

Issue - State: closed - Opened by domenic about 11 years ago - 3 comments
Labels: abstract-underpinnings, make-like-es-spec

#73 - Add spec entry points that don't trigger user code

Issue - State: open - Opened by jorendorff about 11 years ago - 12 comments
Labels: editorial

#72 - Infinite loop

Issue - State: closed - Opened by bryanforbes about 11 years ago - 14 comments
Labels: bug

#71 - What happened to Promise.done()?

Issue - State: closed - Opened by cowwoc about 11 years ago - 2 comments

#70 - Long stack traces

Issue - State: closed - Opened by cowwoc about 11 years ago - 2 comments
Labels: question

#69 - Convert tests to test-262 form

Issue - State: open - Opened by domenic about 11 years ago - 1 comment
Labels: testable-implementation

#68 - Add more tests for the API surface

Issue - State: open - Opened by domenic about 11 years ago - 5 comments
Labels: es-manifestation, testable-implementation

#67 - Clean up testable implementation

Issue - State: closed - Opened by domenic about 11 years ago
Labels: testable-implementation

#66 - Default handler arguments on .then

Issue - State: closed - Opened by rossberg about 11 years ago - 1 comment
Labels: spec-hygeine

#65 - [[PromiseConstructor]] vs .constructor and instanceof

Issue - State: closed - Opened by rossberg about 11 years ago - 10 comments
Labels: question

#64 - Formalize "queue a microtask"

Issue - State: closed - Opened by domenic about 11 years ago - 12 comments
Labels: spec-hygeine, abstract-underpinnings

#63 - `Call` is kind of hacky/poorly named

Issue - State: closed - Opened by domenic about 11 years ago
Labels: spec-hygeine

#62 - Deduplicate thenable coercion, and bring back thenable coercions weak map

Issue - State: closed - Opened by domenic about 11 years ago
Labels: normative-change, abstract-underpinnings

#61 - Potential reentrance bug in CoerceThenable

Issue - State: closed - Opened by domenic about 11 years ago - 1 comment
Labels: bug

#60 - PropagateToDerived should not have to ReturnIfAbrupt

Issue - State: closed - Opened by jorendorff about 11 years ago - 1 comment
Labels: spec-hygeine

#59 - Should cleanup steps be included or omitted?

Issue - State: closed - Opened by domenic about 11 years ago - 1 comment
Labels: spec-hygeine, question

#58 - iterable should be transformed to an iterator

Issue - State: closed - Opened by Nathan-Wall about 11 years ago - 1 comment
Labels: bug, es-manifestation

#57 - Lazy create Derived list at end of PropagateToDerived

Issue - State: closed - Opened by junosuarez about 11 years ago - 6 comments
Labels: question

#56 - Remove IsPromise check from GetDeferred

Issue - State: closed - Opened by domenic about 11 years ago
Labels: normative-change, subclassing

#55 - Should we trap exceptions?

Issue - State: closed - Opened by domenic about 11 years ago - 5 comments
Labels: question, subclassing

#54 - Make Resolve operate the same on promises and thenables, using `then`

Issue - State: closed - Opened by domenic about 11 years ago - 17 comments
Labels: normative-change, subclassing

#53 - Never bypass the `then` method

Issue - State: closed - Opened by domenic about 11 years ago - 2 comments
Labels: normative-change, subclassing

#52 - CallHandle improperly transforms a derived promise.

Issue - State: closed - Opened by 6XGate about 11 years ago - 3 comments
Labels: invalid

#51 - Then call to GetDeferred expects a proper Promise (or subclass) but doesn't verify

Issue - State: closed - Opened by Nathan-Wall about 11 years ago - 2 comments
Labels: bug, abstract-underpinnings, subclassing

#50 - Throw Error if constructor passed to GetDeferred doesn't pass functions?

Issue - State: closed - Opened by Nathan-Wall about 11 years ago - 3 comments
Labels: bug, abstract-underpinnings, subclassing

#49 - Drop dot notation for internal data properties

Issue - State: closed - Opened by Nathan-Wall about 11 years ago - 2 comments
Labels: editorial, make-like-es-spec

#48 - Typo: e => result

Issue - State: closed - Opened by Nathan-Wall about 11 years ago
Labels: editorial

#47 - Testable implementation is starting to lag

Issue - State: closed - Opened by domenic about 11 years ago
Labels: testable-implementation

#46 - Formalize iteration protocol

Issue - State: closed - Opened by domenic about 11 years ago
Labels: spec-hygeine, make-like-es-spec

#45 - Tighten up internal data property treatment

Issue - State: closed - Opened by domenic about 11 years ago - 1 comment
Labels: editorial, make-like-es-spec

#44 - Can sub-classes use additional arguments for "then"?

Issue - State: closed - Opened by skaegi about 11 years ago - 4 comments
Labels: question, subclassing

#43 - Don't coerce Promise in UpdateDerived

Issue - State: closed - Opened by 6XGate about 11 years ago - 2 comments
Labels: invalid

#42 - Overriden `then`s?

Issue - State: closed - Opened by domenic about 11 years ago - 24 comments
Labels: question

#41 - consider a version of Promise.all that works on object

Issue - State: closed - Opened by Raynos about 11 years ago - 5 comments
Labels: question

#40 - Tighten up language around the [[Derived]] list

Issue - State: closed - Opened by domenic about 11 years ago
Labels: make-like-es-spec

#39 - Formalize ThenableCoercions Weak Map

Issue - State: closed - Opened by domenic about 11 years ago - 2 comments
Labels: spec-hygeine, make-like-es-spec

#38 - Use spaces around parens in function/operation definitions

Issue - State: closed - Opened by domenic about 11 years ago
Labels: make-like-es-spec, formatting

#37 - Use bold, italics, and monospace separately

Issue - State: closed - Opened by domenic about 11 years ago - 2 comments
Labels: make-like-es-spec, formatting

#36 - Formalize creating functions that perform abstract operations

Issue - State: closed - Opened by domenic about 11 years ago - 7 comments
Labels: spec-hygeine, make-like-es-spec

#35 - "terminate these steps" should be "return".

Issue - State: closed - Opened by domenic about 11 years ago
Labels: editorial, make-like-es-spec

#34 - Stop using function-call notation

Issue - State: closed - Opened by domenic about 11 years ago - 4 comments
Labels: editorial, make-like-es-spec

#33 - Replace "thenable" with "promise-like"?

Issue - State: closed - Opened by domenic about 11 years ago - 4 comments
Labels: editorial, make-like-es-spec

#32 - "Call `deferred.[[Resolve]](x)`" is imprecise and problematic

Issue - State: closed - Opened by domenic about 11 years ago
Labels: spec-hygeine, make-like-es-spec

#31 - Make subclassing work automatically

Pull Request - State: closed - Opened by domenic about 11 years ago - 11 comments
Labels: subclassing

#30 - Should we make subclassing easy via `this.constructor` (or similar)?

Issue - State: closed - Opened by domenic about 11 years ago - 10 comments
Labels: normative-change, abstract-underpinnings, subclassing

#29 - Remove race() method

Issue - State: closed - Opened by mounirlamouri about 11 years ago - 3 comments
Labels: question

#28 - Fix typo in Promise.all

Pull Request - State: closed - Opened by mounirlamouri about 11 years ago
Labels: editorial

#27 - Fix typo in Promise.race

Pull Request - State: closed - Opened by mounirlamouri about 11 years ago
Labels: editorial

#26 - Handling of promises returned from onRejected

Issue - State: closed - Opened by lukehoban about 11 years ago - 1 comment
Labels: invalid

#25 - Should we use the new Invoke trap?

Issue - State: closed - Opened by domenic about 11 years ago - 7 comments
Labels: normative-change, abstract-underpinnings

#24 - Why shouldn't promise-returning functions throw?

Issue - State: closed - Opened by tabatkins about 11 years ago - 134 comments
Labels: question

#23 - Converting Exceptions to Rejections in Initializer

Issue - State: closed - Opened by ghost about 11 years ago - 27 comments
Labels: question

#22 - Promise(resolver) vs .then(resolve, reject)

Issue - State: closed - Opened by johnjbarton about 11 years ago - 2 comments
Labels: invalid

#21 - Add shorthand "prose hooks" for performing various operations

Issue - State: closed - Opened by domenic about 11 years ago - 3 comments
Labels: editorial

#20 - Should we kill Promise.resolve?

Issue - State: closed - Opened by erights about 11 years ago - 17 comments
Labels: es-manifestation

#19 - Promise.prototype.done

Issue - State: closed - Opened by medikoo about 11 years ago - 149 comments
Labels: question

#18 - Promise.prototype.finally

Issue - State: closed - Opened by domenic about 11 years ago - 27 comments
Labels: es-manifestation

#17 - Should we include Promise.async ?

Issue - State: closed - Opened by erights about 11 years ago - 4 comments
Labels: question

#16 - CoerceThenable missing return

Issue - State: closed - Opened by Nathan-Wall about 11 years ago - 1 comment
Labels: editorial

#15 - "UpdateFromReason" should be "UpdateDerivedFromReason"

Issue - State: closed - Opened by erights about 11 years ago
Labels: editorial

#14 - UpdateDerived insufficiently asynchronous

Issue - State: closed - Opened by erights about 11 years ago - 4 comments
Labels: invalid

#13 - Define Promise.any|some|every

Issue - State: closed - Opened by annevk about 11 years ago - 35 comments
Labels: es-manifestation

#12 - Make sure there's consensus on the name `Promise.cast`.

Issue - State: closed - Opened by domenic about 11 years ago - 1 comment
Labels: consensus-check, es-manifestation

#11 - Fix missing backtick

Pull Request - State: closed - Opened by ForbesLindesay about 11 years ago
Labels: editorial

#10 - Bad promise constructor arguments

Issue - State: closed - Opened by domenic about 11 years ago - 4 comments
Labels: normative-change, es-manifestation

#9 - Parameter to promise constructor

Issue - State: closed - Opened by domenic about 11 years ago - 16 comments
Labels: consensus-check, es-manifestation

#8 - `Promise.as` instead of coercion behavior for `Promise`.

Issue - State: closed - Opened by domenic about 11 years ago - 38 comments
Labels: normative-change, es-manifestation

#7 - Schedule `Get(thenable, "then")` in a new microtask

Issue - State: closed - Opened by domenic about 11 years ago
Labels: bug, normative-change

#6 - Rephrase in terms of completion values

Issue - State: closed - Opened by domenic about 11 years ago - 4 comments
Labels: spec-hygeine, make-like-es-spec

#5 - UpdateFromValueOrReason -> UpdateViaHandlers?

Issue - State: closed - Opened by domenic about 11 years ago
Labels: spec-hygeine

#4 - Update to use "derived update" specification type

Issue - State: closed - Opened by domenic about 11 years ago
Labels: spec-hygeine

#3 - Allow thenables

Issue - State: closed - Opened by domenic about 11 years ago
Labels: normative-change

#2 - Switch to memoizing the result of assimilation

Issue - State: closed - Opened by domenic about 11 years ago - 4 comments
Labels: normative-change, abstract-underpinnings

#1 - Handle infinite recursion cases?

Issue - State: closed - Opened by domenic about 11 years ago - 4 comments
Labels: normative-change, abstract-underpinnings

GitHub / domenic/promises-unwrapping issues and pull requests