[#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:100392] [Ruby master Feature#17260] Promote pattern matching to official feature
From:
marcandre-ruby-core@...
Date:
2020-10-13 16:19:24 UTC
List:
ruby-core #100392
Issue #17260 has been updated by marcandre (Marc-Andre Lafortune). palkan (Vladimir Dementyev) wrote in #note-7: > I have a little concern regarding the potential changes to the current specification that we might need to introduce to improve the performance. > Recently, we introduced a [deconstructed value caching for array patterns](https://github.com/ruby/ruby/pull/3104), which broke the previous non-documented behaviour: it was possible to return different values for `#deconstruct` call within the same `case..in` statement. Now this is fixed (and the performance is improved). I'm glad to read this, I asked for [just that](https://bugs.ruby-lang.org/issues/15881) before It's a perfectly valid constraint IMO. I wouldn't be worried about the fact that we aren't yet caching `#deconstruct_keys`. I can't think of a valid use case for replying different values. We can document that this constraint is projected in the future. ---------------------------------------- Feature #17260: Promote pattern matching to official feature https://bugs.ruby-lang.org/issues/17260#change-88005 * Author: ktsj (Kazuki Tsujimoto) * Status: Open * Priority: Normal * Target version: 3.0 ---------------------------------------- I propose to promote pattern matching to official feature. The current specification is basically fine, but I'd like to reconsider single line pattern matching (`expr in pat`) and suggest removing it once in 3.0. -- 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>