[#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:100389] [Ruby master Feature#17260] Promote pattern matching to official feature
From:
daniel@...42.com
Date:
2020-10-12 21:55:24 UTC
List:
ruby-core #100389
Issue #17260 has been updated by Dan0042 (Daniel DeLorme). matz (Yukihiro Matsumoto) wrote in #note-1: > I have a secret plan to make right hand assignment a replacement for single line pattern match. I find myself liking this idea a lot. In #13683 nobu suggested pattern matching as a replacement for `v = ary.single`, and while `ary in [v]` is conceptually elegant, `ary => [v]` feels a lot more intuitive. In fact, `expr in pattern` can feel so unintuitive that #16670 even suggested to reverse the order; but this would not be an issue if `=>` was used instead of `in`. If `=>` does not allow the full range of pattern matching due to syntax restrictions, maybe consider a different operator like `~>` or those I proposed in #16794. And perhaps `~>` as rightward assignment could also be used to resolve the ambiguity of `=>` described in #16960. ---------------------------------------- Feature #17260: Promote pattern matching to official feature https://bugs.ruby-lang.org/issues/17260#change-88002 * 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>