> I'm not sure what to do for Ruby 3.2. It's a security fix so it qualifies for a backport, but there's other changes included in a version bump. I am a maintainer of REXML. Ruby 3.2 is subject to security fixes, so I believe an upda...naitoh (Jun NAITOH)
(https://github.com/ruby/strscan/pull/123) Added support for string pattern type in https://github.com/ruby/strscan/pull/106. And fix Success Return content. https://github.com/ruby/strscan/commit/6a5acde674naitoh (Jun NAITOH)
(https://github.com/ruby/strscan/pull/111) # Why? To improve the parsing process, I would like to add benchmarks for all parsing processes. ## scan - scan_full(regexp, false, true) == StringScanner#check - scan_full(regexp, false, fals...naitoh (Jun NAITOH)
unnecessary use of `rb_enc_get()` (https://github.com/ruby/strscan/pull/108) - before: #106 ## Why? In `rb_strseq_index()`, the result of `rb_enc_check()` is used. - https://github.com/ruby/ruby/blob/6c7209cd3788ceec01e504d99057f9d3b...naitoh (Jun NAITOH)
## Why? The explanation of x and y is reversed. https://github.com/ruby/ruby/blob/ddbd64400199fd408d23c85f9fb0d7f742ecf9e1/re.c#L251-L256 ``` long rb_memsearch(const void *x0, long m, const void *y0, long n, rb_encoding *enc) { cons...naitoh (Jun NAITOH)
(https://github.com/ruby/strscan/pull/106) It supports non-head match cases such as StringScanner#scan_until. If we use a String as a pattern, we can improve match performance. Here is a result of the including benchmark. ## CRuby It...naitoh (Jun NAITOH)