Skip to content
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

future.cr -> async #15

Closed
wants to merge 2 commits into from
Closed

future.cr -> async #15

wants to merge 2 commits into from

Conversation

watzon
Copy link

@watzon watzon commented Jan 10, 2021

Closes #7

Figured I'd go ahead and PR this and see how you feel about it. As mentioned in #7, my Async::Future is a bit more powerful than the old Future that use to be in the standard library. I've tried to take inspiration from both Python's asyncio and JavaScript's promises.

shard.yml Outdated Show resolved Hide resolved
@caspiano
Copy link
Contributor

The team that maintains this library has its own asynchronous abstraction of Fibers as Promise. We've been using that library in production for a while now and I currently don't have the bandwidth to review your library. I'll merge once I have had time to dig through your library.

@watzon
Copy link
Author

watzon commented Jan 11, 2021

Sounds good man, just trying to help close some issues while I also create some new ones

@watzon
Copy link
Author

watzon commented Jan 11, 2021

Tagged it wrong initially so the build failed, but it should pass now

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate from futures
2 participants