Michael Mayer

@socketman2016 Do you have a use case for that? Doesn't `->wait()` work for you? As far as I can see, `->done($onFulfilled, $onRejected)` can be simulated by: ``` php /** *...

@socketman2016 wrote at https://github.com/reactphp/promise/issues/66#issuecomment-254120920: > **My application handle errors with exceptions and I have a Uncaught exception handler to manage them**, So sometimes I need to consume promise , something...

@socketman2016 I don't feel capable enough of implementing `done` in `guzzle/promises`, at least at the moment. However, possible implementors and the PO need to be convinced that `done` is needed...

> the problem is some of asynchronous codes are not promise . @socketman2016 Thanks for providing some insights. Maybe the following doesn't meet your requirements, I don't know how your...

 > I think in pure promise-based approach it will be spaghetti code Promises want to make working with asynchronous operations much more pleasant. Joining asynchronous parts is quite easy:...

> This is very hard coded always we must do a boring job , C'mon! Nobody would do it that way. The promise based approach forces one to follow some...

> But I cannot understand why in fixStacktrace we have […] `catch (Throwable $err)` > Or may be just > > ``` php > return new Exception($error); > ``` In...

> I want to know what you think about `trait` , `interface` and `Inheritance` in my approach I can use all of them and for example `override` a method in...

@vdemedes I want to simplify some [`cpy`](https://github.com/sindresorhus/cpy) tests. Calling `path.join` everywhere sucks, and make the code less readable, e.g.: ``` js test.beforeEach(t => { t.context = tempfile(); }); test('cwd', async...

@vdemedes Thank you for reminding me of destructuring assignments, these will really help a lot. > Having `t.context` as a function is not logical to me. Btw, but only if...