5 ms·
I haven't benchmarked it, but it could probably just be a drop-in replacement as I believe the arguments are compatible. Would be interesting to try!
by kcbanner 5y ago
I haven't benchmarked it, but it could probably just be a drop-in replacement as I believe the arguments are compatible. Would be interesting to try!
- pmarreck 5y agoLikely. The dude who developed ripgrep spent like 2 man-years on it full-time, apparently. Interesting (long, detailed) blog post about it: https://blog.burntsushi.net/ripgrep/ https://blog.burntsushi.net/ripgrep/
- burntsushi 5y agoI don't think it took that much time. If you count the time involved in the regex engine though, you might get a bit closer. :-)
- muixoozie 5y agoThanks for all your hardwork! I've been dabbling in Rust and doing toy projects, but have years of experience in other languages. Are there any rust projects you recommend contributing to that have a good community?
- burntsushi 5y agoRust itself for sure. And rust-analyzer. I'm sure there are more. :-)
- pmarreck 5y agoLOL. I thought I read that somewhere in your blog post about it (which was amazingly detailed and interesting), but human minds are poo. Thanks so much for this sweet tool! Is there a ripgrep lib that other software can build on this, btw?
- burntsushi 5y agoTechnically yes, and this is the best I can offer: https://github.com/BurntSushi/ripgrep/issues/1009 https://github.com/BurntSushi/ripgrep/issues/1009 In practice, there's no real high level documentation. And there is still a considerable amount of "glue" code in ripgrep's main executable. So the library layer exists at a lower level of abstraction, which may or may not be okay for your use case.