Tab Atkins Jr.
jackalmage at gmail.com
Mon Aug 19 13:52:35 PDT 2013
On Mon, Aug 19, 2013 at 12:50 PM, Ron Buckton <rbuckton at chronicles.org> wrote:
> Promise.fulfill/PromiseSource#fulfill made sense when there was no unwrap on the input side of Promise#then:
> With all the changes to Promise (addition of Promise#flatMap, recursive unwrap on input side of Promise#then, etc.), it does seem that fulfill's use case has become a bit muddled. I'll admit to still being partial to the earlier design (fulfill/resolve/reject, adopt without recursive unwrap/flattening) as it was a much simpler and more straightforward API.
Yup, having unwrapping both on the value side (in the form of
Promise.resolve()) and on the read side (in the form of .then()) is
just confusing, and doesn't offer any new abilities.
More information about the es-discuss