Regex currently has an optimization that looks to see whether the pattern begins with a set loop followed by some literal, in which case it can optimize the search for matches by searching for the literal and then walking backwards through the starting set. However, it's missing a handful of cases we can easily support:

• It currently gives up if the set loop is wrapped in an atomic and/or a capture.
• It currently gives up if the literal is a set that's wrapped in an atomic, capture, concatenate, loop, or lazy loop.
• If the set loop is followed by an ignore-case string, it currently only searches for the starting set of that string, rather than more of it.
• If the literal is a set, we'd only examine it if it was exactly one iteration (RegexNodeKind.Set) rather than a loop with at least one iteration.

This fixes all of those issues, such that the optimization extends to more patterns. In our regex database, there are currently 189 patterns that lead to using this optimization. With this change, that increases to 331.

Based on benchmark fromhttps://github.com/BurntSushi/rebar#ruff-noqa:

usingBenchmarkDotNet.Attributes;usingBenchmarkDotNet.Running;usingSystem.Text.RegularExpressions;BenchmarkSwitcher.FromAssembly(typeof(Tests).Assembly).Run(args);[HideColumns("start","end","Error","StdDev","Job")]publicpartialclassTests{privatestaticreadonlyRegexs_regex=newRegex("(\\s*)((?i:# noqa)(?::\\s?(([A-Z]+[0-9]+(?:[,\\s]+)?)+))?)",RegexOptions.Compiled);privatestaticstrings_haystack=newHttpClient().GetStringAsync("https://raw.githubusercontent.com/BurntSushi/rebar/master/benchmarks/haystacks/wild/cpython-226484e4.py").Result;[Benchmark]publicintLineByLine(){inttotal=0;foreach(ReadOnlySpan<char>lineins_haystack.AsSpan().EnumerateLines()){total+=s_regex.Count(line);}returntotal;}[Benchmark]publicintAll()=>s_regex.Count(s_haystack);}