Why do we have Amp\Future about amp HOT 7 CLOSED

Amp\Future is meant to be used inside libraries, i.e. it never should cross public API boundaries, correct.

from amp.

Why do we have it now? Why not just Deferred as we had previously?

from amp.

I'm not 100% sure why it's necessary. The only difference is it saving us from a single ->getAwaitable() call. I do not think this is worth it…

But perhaps I'm missing something and @trowski can tell.

from amp.

That's exactly why this issue exists.

from amp.

Future (and Producer for observables) only exists to avoid the function call to retrieve the awaitable (or observable) when the object will never be exposed to a public API. It's a minor performance bump, but if the confusion isn't worth it, Deferred and Postponed can be used instead.

from amp.

We didn't need it in Amp v1, I don't think we need it in Amp v2. It adds more confusion than a single method call can save us.

from amp.

Resolved by removal.

from amp.