-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Rename project? #13
Labels
Comments
I think this is a good idea. I like |
Yeah, I think |
I also like |
mre
added a commit
that referenced
this issue
Dec 6, 2019
mre
added a commit
that referenced
this issue
Dec 6, 2019
mre
added a commit
that referenced
this issue
Dec 6, 2019
mre
added a commit
that referenced
this issue
Dec 6, 2019
Rename project to futures-batch (fixes #13)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Rust async ecosystem is moving fast and this crate no longer depends on Tokio.
The only dependency we have is on
Stream
from thefutures
crate.I was wondering if we should reflect that in the project name.
The two names that I favor at the moment are
futures-batch
andasync-batch
with a slight tendency towardsfutures-batch
. I consideredstream-batch
, but it doesn't have the same ring to it.Would be interested in getting your opinions @doyoubi, @leshow, @spebern, and @wngr.
The text was updated successfully, but these errors were encountered: