[#100309] How to use backport custom field — Jun Aruga <jaruga@...>
Please allow my ignorance.
9 messages
2020/10/06
[#100310] Re: How to use backport custom field
— "NARUSE, Yui" <naruse@...>
2020/10/06
IkJhY2twb3J0IGN1c3RvbSBmaWVsZCIgaXMgb25seSBhdmFpbGFibGUgZm9yIHRpY2tldHMgd2hv
[#100311] Re: How to use backport custom field
— Jun Aruga <jaruga@...>
2020/10/06
On Tue, Oct 6, 2020 at 4:44 PM NARUSE, Yui <[email protected]> wrote:
[#100314] Re: How to use backport custom field
— "NARUSE, Yui" <naruse@...>
2020/10/06
VGhhbmsgeW91IGZvciBjb25maXJtYXRpb24uCkkgY2hlY2tlZCBhZ2FpbiBhbmQgdG8gZWRpdCBi
[#100322] Re: How to use backport custom field
— Jun Aruga <jaruga@...>
2020/10/07
On Tue, Oct 6, 2020 at 7:25 PM NARUSE, Yui <[email protected]> wrote:
[#100326] Re: How to use backport custom field
— "NARUSE, Yui" <naruse@...>
2020/10/07
SSBhZGRlZCB5b3UgdG8gIlJlcG9ydGVyIiByb2xlIGluIHRoZSBwcm9qZWN0CgoyMDIw5bm0MTDm
[#100327] Re: How to use backport custom field
— Jun Aruga <jaruga@...>
2020/10/07
On Wed, Oct 7, 2020 at 1:42 PM NARUSE, Yui <[email protected]> wrote:
[ruby-core:100443] [Ruby master Feature#17256] Freeze all Regexp objects
From:
ko1@...
Date:
2020-10-20 06:25:10 UTC
List:
ruby-core #100443
Issue #17256 has been updated by ko1 (Koichi Sasada).
I tried it and several errors are observed on tests.
It is possible that people want to tweak Regexp objects (unlike Range objects).
How about to freeze literals includes `/#{expr}/`?
https://github.com/ruby/ruby/pull/3676
It is easy to fix by `.dup` method.
----------------------------------------
Feature #17256: Freeze all Regexp objects
https://bugs.ruby-lang.org/issues/17256#change-88058
* Author: ko1 (Koichi Sasada)
* Status: Open
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
----------------------------------------
To be shared between ractors, Regexp objects should be frozen.
Now, Matz has proposed to make all Regexp objects frozen.
Ten months ago, there was a note https://bugs.ruby-lang.org/issues/16377#note-7 :
> For the record: Regexp.new should continue to return unfrozen Regexp instance.
So I'm not sure whether it is a good way or not.
Could you give me your comment on it?
If no comments are given, I'll try to freeze them before Ruby 3.0 preview 2.
BTW, I believe `/#{expr}/o` should be frozen because this expression only returns one Regexp object.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>