thyresias (Thierry Lambert) wrote in #note-4: > Ok for the workaround, but don't you think all this is inconsistent? > ... I agree this represents a bug, which is why I changed the status back to Open. However, I think the bug is in th...jeremyevans0 (Jeremy Evans)
thyresias (Thierry Lambert) wrote in #note-2: > > Does this behavior cause any problems in your application? > ... Thank you for providing an example. This seems more like an issue with the literal Regexp support in general than with `...jeremyevans0 (Jeremy Evans)
This is not a bug, it is deliberate behavior for ASCII-only strings in `rb_reg_quote` (internal function called by `Regexp.escape`): ```c if (ascii_only) { rb_enc_associate(tmp, rb_usascii_encoding()); } ``` `US...jeremyevans0 (Jeremy Evans)
I've submitted a PR that implements backwards compatibility for Set subclasses, without affecting Set itself: https://github.com/ruby/ruby/pull/15228 @Eregon can you try it with concurrent-ruby and see if it resolves your issue?jeremyevans0 (Jeremy Evans)
Eregon (Benoit Daloze) wrote in #note-13: > jeremyevans0 (Jeremy Evans) wrote in #note-11: > ... I submitted a pull request that implements what @knu suggested: https://github.com/ruby/ruby/pull/15228 It allows subclasses to use the...jeremyevans0 (Jeremy Evans)
wsfulton (William Fulton) wrote in #note-4: > Fixing this warning, in particular, removes undefined behaviour. Can you explain what the undefined behavior is? My understanding is that in both C and C++, the behavior is defined to ze...jeremyevans0 (Jeremy Evans)
wsfulton (William Fulton) wrote in #note-2: > This happens when compiling an EXTENSION. We have always used -Wmissing-field-initializers in our extensions and now they are broken. New Ruby releases really MUST NOT introduce new warnings...jeremyevans0 (Jeremy Evans)
tenderlovemaking (Aaron Patterson) wrote in #note-10: > mame (Yusuke Endoh) wrote in #note-9: > ... I agree with @mame and @tenderlovemaking. Removing special handling of infinite ranges avoids the original issue (calling `size`), as ...jeremyevans0 (Jeremy Evans)
Dan0042 (Daniel DeLorme) wrote in #note-24: > So the issue here is that pathname doesn't use this `rb_provide` ? pathname does use `rb_provide`: ``` $ git grep rb_provide pathname.c pathname.c: rb_provide("pathname.so"); ```...jeremyevans0 (Jeremy Evans)
jeremyevans0 (Jeremy Evans)09:50 PM Ruby Bug #21709: Inconsistent encoding by Regexp.escape