A couple of weeks ago we announced the upgrade of Crystal’s regex engine to PCRE2. The upgraded engine is used by default in nightly releases and can be optionally tested in Crystal 1.7 with the
-Duse_pcre2 flag (we recommend 1.7.3 for that).
We have since received some feedback from the community. Besides positive and mostly (i.e. only requiring minor adjustments) reports, we’ve seen a guide about diligent compatibility testing and some critical comments on the transition process. I am not aware of any reports about major issues with the upgrade. That’s a good sign, but we should get more meaningful insights.
So I’m asking you to respond to this poll to help gauge the effect of the PCRE2 transition in the Crystal ecosystem.
The poll is open for everybody, no matter if you’re an Open Source shard author, hacking a personal project, working on a professional product or just building somebody else’s code.
Please select all that apply, especially when working with multiple Crystal projects.
- Everything works fine with PCRE2
- PCRE2 broke some code and I’m opting out for now
- PCRE2 broke some code and I have updated my project to support it
- I have not tried PCRE2 yet
- I do not use regular expressions in my projects
Please leave a comment with some details if anything may need clarification. For example what kind of failures you have seen or why you’re planning to stay away from PCRE2.
Thanks for your participation