@geofflangdale Well, it finally happened. Someone has started a patch to integrate Hyperscan into ripgrep. Turns out to be marvelously faster than my regex engine (as is expected :-)).https://github.com/BurntSushi/ripgrep/issues/1488 …
-
-
Replying to @burntsushi5
Interesting. I would think that either cherry-picking the subsystems of Hyperscan that provide the most performance benefit and integrating them into ripgrep, or cherry-picking the features they want from ripgrep and integrating them into HS or its tools, would be the way.
1 reply 0 retweets 2 likes
Replying to @geofflangdale
Both of those sound like a tremendous amount of work compared to this approach honestly. ripgrep already supports two different regex engines. I built it such that _most_ pieces are agnostic to the underlying engine.
4:16 PM - 16 Feb 2020
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.