[#75687] [Ruby trunk Bug#12416] struct rb_id_table lacks mark function — shyouhei@...
Issue #12416 has been reported by Shyouhei Urabe.
3 messages
2016/05/23
[#75763] [Ruby trunk Feature#12435] Using connect_nonblock to open TCP connections in Net::HTTP#connect — mohamed.m.m.hafez@...
Issue #12435 has been reported by Mohamed Hafez.
3 messages
2016/05/28
[#75774] Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock — Mohamed Hafez <mohamed.m.m.hafez@...>
Hi all, every now and then in my production server, I'm
4 messages
2016/05/30
[#75775] Re: Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock
— Mohamed Hafez <mohamed.m.m.hafez@...>
2016/05/30
Or does MRI's OpenSSL::SSL::SSLSocket#connect_nonblock just return
[#75782] Important: Somewhat backwards-incompatible change (Fwd: [ruby-cvs:62388] duerst:r55225 (trunk): * string.c: Activate full Unicode case mapping for UTF-8) — Martin J. Dürst <duerst@...>
With the change below, I have activated full Unicode case mapping for
4 messages
2016/05/31
[ruby-core:75552] [Ruby trunk Feature#8895] Destructuring Assignment for Hash
From:
matz@...
Date:
2016-05-17 08:18:59 UTC
List:
ruby-core #75552
Issue #8895 has been updated by Yukihiro Matsumoto.
The proposed syntax is much harder to implement than it looks. It conflicts with Hash literals. As a result, humans can be confused as well.
Probably this kind of problems should be addressed by pattern matching, which we are considering to add to Ruby in the future.
Matz.
----------------------------------------
Feature #8895: Destructuring Assignment for Hash
https://bugs.ruby-lang.org/issues/8895#change-58683
* Author: Jack Chen
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Given Ruby already supports destructuring assignment with Array (a, b = [1, 2]), I propose destructuring assignments for Hash.
Basic example
-------------
```ruby
params = {name: "John Smith", age: 42}
{name: name, age: age} = params
# name == "John Smith"
# age == 42
```
This would replace a common pattern of assigning hash values to local variables to work with.
General syntax
--------------
```ruby
{ <key-expr> => <variable_name>, … } = <object that responds to #[]>
# Symbols
{ foo: bar } = { foo: "bar" }
bar == "bar"
# Potential shorthand
{ foo } = { foo: "bar" }
foo == "bar"
```
Use cases
---------
```ruby
# MatchData
{ username: username, age: age } = "user:jsmith age:42".match(/user:(?<username>\w+) age:(?<age>\d+)/)
username == "jsmith"
age == "42"
```
Edge cases
----------
```ruby
# Variable being assigned to more than once should use the last one
{ foo: var, bar: var } = {foo: 1, bar: 2}
var == 2
```
Thoughts?
--
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>