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

ack closed the issues linked in the readme #803

Closed
ljedrz opened this issue Feb 14, 2018 · 1 comment
Closed

ack closed the issues linked in the readme #803

ljedrz opened this issue Feb 14, 2018 · 1 comment
Labels
question An issue that is lacking clarity on one or more points.

Comments

@ljedrz
Copy link

ljedrz commented Feb 14, 2018

ack seems to have closed the bugs that are linked in the readme. The other tools have also probably progressed since 2016.

It would probably be a good idea to re-run the benchmark so it's up to date.

@BurntSushi
Copy link
Owner

BurntSushi commented Feb 14, 2018

ack seems to have closed the bugs that are linked in the readme.

As the issues you've linked state, they are not fixed in ack2 but are fixed in ack3. ack3 is currently under development. Once ack3 becomes the official stable release, I'll update the benchmark to use ack3.

The other tools have also probably progressed since 2016.

Indeed! That's why I periodically update them.

The benchmarks in the README are meant to give a rough glance. If you want more detailed benchmarks, then see my blog post, which is also linked in the README. The blog post gets updated far less frequently because it is a lot of work. It will happen at my own discretion.

@BurntSushi BurntSushi added the question An issue that is lacking clarity on one or more points. label Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question An issue that is lacking clarity on one or more points.
Projects
None yet
Development

No branches or pull requests

2 participants