Question 1

How do I switch from Go's standard regexp to coregex?

Accepted Answer

Replace imports with github.com/coregx/coregex and use coregex.MustCompile identically; the API is fully compatible, so existing code works with minimal changes. See the quick start example for a drop-in replacement.

Question 2

Is coregex faster than Rust's regex crate?

Accepted Answer

It depends on the pattern; benchmarks show coregex is up to 18.8x faster for IP matching but 6.2x slower for literal alternation. Generally, it's within 1-6x of Rust's performance, with some wins like multiline patterns.

Question 3

Does coregex support regex backreferences?

Accepted Answer

No, coregex excludes backreferences to ensure O(n) time complexity and prevent ReDoS vulnerabilities. If you need them, consider regexp2, but be aware of exponential worst-case performance.

Question 4

What CPU features are needed for SIMD optimizations?

Accepted Answer

Coregex uses AVX2 and SSSE3 instructions on AMD64 architectures for prefilters like memchr and Teddy; on other CPUs, it falls back to pure Go code, which may reduce speedups in performance-critical scenarios.

Question 5

Is coregex thread-safe for concurrent use?

Accepted Answer

Yes, compiled Regexp objects are safe to share across goroutines, using internal sync.Pool for state management, similar to stdlib regexp. This is explicitly stated in the thread safety section.

Question 6

How does coregex handle Unicode character classes?

Accepted Answer

It supports Unicode via Go's regexp/syntax parser, including features like \p{L} and \P{N}, with optimizations for common patterns, though performance details for complex Unicode are not highlighted in benchmarks.

coregex

What is coregex?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions