[#66678] [ruby-trunk - Feature #10481] Add "if" and "unless" clauses to rescue statements — alex@...
Issue #10481 has been updated by Alex Boyd.
3 messages
2014/12/04
[#66762] Re: [ruby-changes:36667] normal:r48748 (trunk): struct: avoid all O(n) behavior on access — Tanaka Akira <akr@...>
2014-12-10 0:44 GMT+09:00 normal <ko1@atdot.net>:
3 messages
2014/12/10
[#66851] [ruby-trunk - Feature #10585] struct: speedup struct.attr = v for first 10 attributes and struct[:attr] for big structs — funny.falcon@...
Issue #10585 has been updated by Yura Sokolov.
3 messages
2014/12/15
[#67126] Ruby 2.2.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 2.2.0.
8 messages
2014/12/25
[#67128] Re: Ruby 2.2.0 Released
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2014/12/25
I can't install it in any of our Ubuntu servers using rbenv:
[#67129] Re: Ruby 2.2.0 Released
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/12/25
> I can't install it in any of our Ubuntu servers using rbenv:
[ruby-core:66600] [ruby-trunk - misc #10541] Remove shorthand string interpolation syntax
From:
nobu@...
Date:
2014-12-01 03:38:49 UTC
List:
ruby-core #66600
Issue #10541 has been updated by Nobuyoshi Nakada. Martin D端rst wrote: > Maybe what we can do is to just produce a warning, without depreciation? That will help everybody who wants to avoid this syntax, and will also help programmers to get to know and learn it. What kind of warnings? To warn all `#@ivar` things just makes it boring and would discourage it. Uninitialized instance variables are already warned when `$VERBOSE`. ---------------------------------------- misc #10541: Remove shorthand string interpolation syntax https://bugs.ruby-lang.org/issues/10541#change-50217 * 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/