[#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
"Backport custom field" is only available for tickets whose tracker is "Bug".
[#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 <naruse@airemix.jp> wrote:
[#100314] Re: How to use backport custom field
— "NARUSE, Yui" <naruse@...>
2020/10/06
Thank you for confirmation.
[#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 <naruse@airemix.jp> wrote:
[#100326] Re: How to use backport custom field
— "NARUSE, Yui" <naruse@...>
2020/10/07
I added you to "Reporter" role in the project
[#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 <naruse@airemix.jp> wrote:
[#100358] [BUG] ruby 2.6.6 warning with encdb.so — shiftag <shiftag@...>
Hello,
1 message
2020/10/10
[ruby-core:100350] [Ruby master Feature#17195] Freeze Enumerator::ArithmeticSequence objects
From:
eregontp@...
Date:
2020-10-09 18:15:37 UTC
List:
ruby-core #100350
Issue #17195 has been updated by Eregon (Benoit Daloze). Status changed from Open to Rejected Right, that makes sense, thanks for the reply. Interestingly it seems `Enumerator#next` is still allowed even if the Enumerator is frozen, even though it is a kind of mutation. I think that's a bug. Given `ArithmeticSequence` has state through being an Enumerator, I think it's not reasonable to freeze, so I'll reject this issue. ---------------------------------------- Feature #17195: Freeze Enumerator::ArithmeticSequence objects https://bugs.ruby-lang.org/issues/17195#change-87962 * Author: Eregon (Benoit Daloze) * Status: Rejected * Priority: Normal ---------------------------------------- Now, all Ranges are frozen (#15504). Enumerator::ArithmeticSequence is very similar to Range, just with an extra `step`. They're essentially already immutable, except that one could use set instance variables, but it seems of little use. So, should we make Enumerator::ArithmeticSequence frozen too? -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>