-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why do we have Amp\Future #49
Comments
Amp\Future is meant to be used inside libraries, i.e. it never should cross public API boundaries, correct. |
Why do we have it now? Why not just |
I'm not 100% sure why it's necessary. The only difference is it saving us from a single But perhaps I'm missing something and @trowski can tell. |
That's exactly why this issue exists. |
|
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. |
Resolved by removal. |
What's the purpose of
Amp\Future
? It's documented to be used only in internal code, no public APIs?The text was updated successfully, but these errors were encountered: