[#66126] Creation/Conversion methods/functions table for Ruby types — SASADA Koichi <ko1@...>
Hi,
5 messages
2014/11/07
[#66248] [ruby-trunk - Feature #10423] [PATCH] opt_str_lit*: avoid literal string allocations — normalperson@...
Issue #10423 has been updated by Eric Wong.
3 messages
2014/11/13
[#66595] [ruby-trunk - Bug #10557] [Open] Block not given when the argument is a string — bartosz@...
Issue #10557 has been reported by Bartosz Kopinski.
3 messages
2014/11/30
[ruby-core:66592] [ruby-trunk - misc #10541] Remove shorthand string interpolation syntax
From:
sawadatsuyoshi@...
Date:
2014-11-30 13:54:29 UTC
List:
ruby-core #66592
Issue #10541 has been updated by Tsuyoshi Sawada.
> Most experienced Ruby developers I've talked to don't even know it exists
Probably those developers are not experienced enough.
> When a syntax is not widely known and has the potential for problems,
then developers should study more.
> It has been the cause of real problems
That is just a bug.
> most Ruby editors will insert {} after #
It is those editors to blame, not the syntax.
> I prefer unambiguous syntax.
The syntax is not ambiguous. If it were, Ruby would not have been implemented.
> This syntax is very confusing
Never to me.
> The fact that it is still rarely used
This is false.
I think the real problem is that Ruby has not been well documented. Documentation should be comprehensive and should include description about such behaviour.
----------------------------------------
misc #10541: Remove shorthand string interpolation syntax
https://bugs.ruby-lang.org/issues/10541#change-50209
* Author: Daniel Morrison
* Status: Open
* Priority: Normal
* Assignee: Yukihiro Matsumoto
* Category: syntax
* Target version: current: 2.2.0
----------------------------------------
I would like to see the shorthand string interpolation syntax, "foo#@bar" deprecated and then removed in 3.0.
My reasons:
1. Most experienced Ruby developers I've talked to don't even know it exists.
2. It has been the cause of real problems. http://status.cloudamqp.com/incidents/vj62pnp62tj9
When a syntax is not widely known and has the potential for problems, I think it makes sense to deprecate and remove.
--
https://bugs.ruby-lang.org/