You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My first thought is that this looks like a symptom of #38 -- detecting extended grapheme clusters can be really slow -- but the NSRegularExpression example also (incorrectly) uses .characters.count here, so there's something else going on in the library, too.
I've managed to track it down to the MatchSequence.Iterator. I believe the performance drop is attributed to the Match initializations that occur within the iterator. You can see the temporary heap allocations are almost doubled.
You can play around with the test cases in the performance branch on my fork.
Love the syntax. Love the features. But performance goes bad on large strings. Here's the test for digesting a crashlog.
The text was updated successfully, but these errors were encountered: