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

Rename project? #13

Closed
mre opened this issue Dec 5, 2019 · 3 comments
Closed

Rename project? #13

mre opened this issue Dec 5, 2019 · 3 comments

Comments

@mre
Copy link
Owner

mre commented Dec 5, 2019

The Rust async ecosystem is moving fast and this crate no longer depends on Tokio.
The only dependency we have is on Stream from the futures 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 and async-batch with a slight tendency towards futures-batch. I considered stream-batch, but it doesn't have the same ring to it.

Would be interested in getting your opinions @doyoubi, @leshow, @spebern, and @wngr.

@leshow
Copy link
Contributor

leshow commented Dec 5, 2019

I think this is a good idea. I like futures-batch also; I think it will be more discoverable than async-batch.

@doyoubi
Copy link
Contributor

doyoubi commented Dec 6, 2019

Yeah, I think futures-batch is easier to be found since it's relying on the futures ecosystem.

@spebern
Copy link

spebern commented Dec 6, 2019

I also like futures-batch.

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 mre closed this as completed in 7db1957 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
Projects
None yet
Development

No branches or pull requests

4 participants