From: sawadatsuyoshi@gmail.com
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:51005] [Ruby master Feature#17597] 直後の改行を無視する命令（......）
Date: Sat, 30 Jan 2021 15:13:21 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-90181.20210130151320.2@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-17597.20210130094058.2@ruby-lang.org>
Issue #17597 has been updated by sawa (Tsuyoshi Sawada).
This is a duplicate of #17598.
----------------------------------------
Feature #17597: 直後の改行を無視する命令（......）
https://bugs.ruby-lang.org/issues/17597#change-90181
* Author: Anonymous
* Status: Open
* Priority: Normal
----------------------------------------
改行を無視する命令、今 \(\n) となっている命令についてです。 ...... を提案します。
(0... ......
5).each ......
.map{_1} ...... # some comments
=> ar
# (0...5).each.map{_1} => ar
(1) 本当は ... が一番良いと思います。しかし Range で使われています。
(2) 一番良いのが使えないなら長くしよう。 ......
(3) 実際に使うのなら .... が妥当？
(4) .... と ...... の両方作っちゃえ。
私は実験的に (2) を希望します。
--
https://bugs.ruby-lang.org/
parent reply other threads:[~2021-01-30 15:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <redmine.issue-17597.20210130094058.2@ruby-lang.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-90181.20210130151320.2@ruby-lang.org \
--to=sawadatsuyoshi@gmail.com \
--cc=ruby-dev@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).