[#84280] [Ruby trunk Bug#14181] hangs or deadlocks from waitpid, threads, and trapping SIGCHLD — nobu@...
Issue #14181 has been updated by nobu (Nobuyoshi Nakada).
3 messages
2017/12/15
[#84398] [Ruby trunk Bug#14220] WEBrick changes - failures on MSWIN, MinGW — Greg.mpls@...
Issue #14220 has been reported by MSP-Greg (Greg L).
3 messages
2017/12/22
[#84472] Re: [ruby-dev:50394] [Ruby trunk Bug#14240] warn four special variables: $; $, $/ $\ — Eric Wong <normalperson@...>
Shouldn't English posts be on ruby-core instead of ruby-dev?
3 messages
2017/12/26
[ruby-core:84517] [Ruby trunk Feature#14249] Remove str[match_str]
From:
naruse@...
Date:
2017-12-27 16:12:23 UTC
List:
ruby-core #84517
Issue #14249 has been updated by naruse (Yui NARUSE).
Use Hash#dig instead.
----------------------------------------
Feature #14249: Remove str[match_str]
https://bugs.ruby-lang.org/issues/14249#change-69046
* Author: ana06 (Ana Maria Martinez Gomez)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
I wonder if `str[match_str]` makes sense.
``` Ruby
"ana"['a'] => "a"
```
I would say this is not expected and it brings problems, for example when accessing nested hashes. For example:
``` Ruby
params = { "user" => "Nicolas Cage" } => {"user"=>"Nicolas Cage"}
params["user"]["age"] => "age"
```
I think `str[regexp]` is enough and that `str[match_str]` can be removed.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>