This summary was "very easy", because it is wrong. This assessment is unfair to RE2, and we're comparing to RE2 because it's the only one of these that can do multiple regex. Both Hyperscan and RE2 throw a good deal of regex under the bus in order to get multiple regex support, performance and/or streaming capability.
Oops. We're out of date in our thinking then. If the implementation is similar to re2, you'll probably see similar performance, although I hear good things about your small group literal matcher. :-)
:P Yeah, I would expect performance characteristics to be very similar to RE2! I actually think RegexSet disables literal optimizations in more cases than the standard regex, but it's been a while since I've touched that.
My summary is from the language implementor point of view, not from the POV of the 1% users which do need regex sets (batch regex searching), no backtracking and fast streaming.
For fast streaming there would be sregex as first contender of Hyperscan, not RE2.
RE2 is fine, but nobody uses it because... What do you think why?
Because of no backtracking support.
If I need a limited fast regex on modern intel-CPU's with SIMD, I'll choose Hyperscan over everything else. But I need to check the cpu capabilities before loading the shared lib.
If I need a fast regex everywhere else, I choose PCRE2 over everything else. RE2 had its time for the last decade, but this time is over now.
