See <https://bugs.ruby-lang.org/issues/19417#note-3>. https://unicode.org/reports/tr18/#word states word should match join_control chars. It did not previously: ```ruby [*0x0..0xD799, *0xE000..0x10FFFF].map { |n| n.chr 'utf-8' } => al...janosch-x (Janosch Müller)
byroot (Jean Boussier) wrote in #note-73: > it probably doesn't make a huge difference, but your regexp is a bit too strict It probably makes even less of a difference, but magic comments are also indentable, case-insensitive, and ca...janosch-x (Janosch Müller)
... to conform to UTS 18 as mentioned in https://bugs.ruby-lang.org/issues/19417#note-3 https://unicode.org/reports/tr18/#word states word should match join_control chars. It currently does not: ```ruby [*0x0..0xD799, *0xE000..0x10FFF...janosch-x (Janosch Müller)
Hi @mame! As mentioned in the ticket, i could not reproduce it with a smaller setup. Maybe problems only begin at a certain size, or when there is some `require` hierarchy? I've now forked my affected repository to demonstrate t...janosch-x (Janosch Müller)
I have a large rspec test suite. I found that if I call a Ractor, the Coverage results are strongly affected, i.e. almost all files appear to be uncovered. This happens even if I only ever call a Ractor before the library or rspec are re...janosch-x (Janosch Müller)
Dan0042 (Daniel DeLorme) wrote in #note-13: > it opens a big can of worms in terms of where do you draw the line for how the 'destructive' flag propagates? Which of those foo methods would you consider to be destructive? I was really...janosch-x (Janosch Müller)
Dan0042 (Daniel DeLorme) wrote in #note-10: > For regular ruby code, probably the only way to know if a method is destructive is to check for instance variable assignments. A lot of everyday Ruby code seems to be destructive, not s...janosch-x (Janosch Müller)
janosch-x (Janosch Müller)10:17 PM Ruby Revision 5a42d267 (git): Make word prop match join_control to conform to UTS 18