My impression is that this proposal is useful in some cases, but these are too rare to include it in core. This functionality is better suited for a gem. Maybe it's already available in some gem.duerst (Martin Dürst)
I think we should use "security in depth" here, and not treat this as an exclusive OR. We should be very clear that it may be unsafe to create a Regexp from untrusted input. We can fix (and should) fix the documentation as quickly as pos...duerst (Martin Dürst)
Just some comments to hopefully help this issue move forward. `unicode_normalize` uses two hashes, `UnicodeNormalize::NF_HASH_C` and `UnicodeNormalize::NF_HASH_D`. These hashes are used to cache results of composition (`NF_HASH_C`) or...duerst (Martin Dürst)
What about methods such as `gsub`/`gsub!`, where the return value of `gsub!` is `nil` if there is no change? That may create a problem if e.g. multiple `gsub`s are chained and converted to `gsub!`s.duerst (Martin Dürst)
Dan0042 (Daniel DeLorme) wrote in #note-3: > Indeed, but I believe "ＵＴＦ－八" would be a better alias here Fully agree. I was just too lazy to go figure out the full-width hyphen, sorry. duerst (Martin Dürst)
Thanks to @ko1 for this timely news. It looks like the current Japanese government is recently taking some steps that in some ways have felt long overdue. On December 22, 2025, they changed the Romanization used by the Government from 'K...duerst (Martin Dürst)
Here is another proposal: Why not count using administrative/fiscal years? The administrative/fiscal year (年度 ('nendo') in Japanese, as opposed to simply 年 for (calendar) year) starts on April 1st. As an example, 1993-02-24 to 1993-3-...duerst (Martin Dürst)
Using two or more overlapping Unicode properties may not be very frequent, but in most cases isn't a mistake. If a user writes `/[\p{Word}\p{S}]/`, that expression should just match all word characters and all symbol characters, because ...duerst (Martin Dürst)
nagachika (Tomoyuki Chikanaga) wrote in #note-1: > In my environment, removing `exts.mk` in build directory resolved the issue. This worked for me, too.duerst (Martin Dürst)
duerst (Martin Dürst)06:53 AM Ruby Feature #22536: Add Enumerable#longest_slice to return the range of the longest consecutive matching sequence