Issue #9047 has been updated by matz (Yukihiro Matsumoto).

Assignee set to matz (Yukihiro Matsumoto)
Target version set to next minor

@mohawkjohn let us separate the issue.  There may be a chance to introduce num:num literals for your purpose (just maybe).

@jamonholmgren having Symbol GC, it is realistic to have that kind of notation to cope well with JSON.  But I am still not sure how much useful this is.  Any use-case?

Matz.

----------------------------------------
Feature #9047: Alternate hash key syntax for symbols
https://bugs.ruby-lang.org/issues/9047#change-42586

Author: jamonholmgren (Jamon Holmgren)
Status: Open
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: 
Target version: next minor


=begin

In Ruby, if you can create a symbol with ((|:"symbolname"|)), it seems consistent to allow moving the colon to the right side in a hash and dropping the hash rocket (=>).


 {
   :str => "v",   # symbol
   str: "v",      # symbol
   :"str" => "v", # symbol
   "str": "v",    # should also be a symbol
 }
 
 
It would look like this:

 h = {
   "mykey": "value",
   "otherkey": "othervalue",
   regular_symbol: "value"
 }

String and other non-symbol keys would retain the hash rocket syntax to avoid ambiguity.

 {
   "string" => "v",
   MyObj.new => "v",
   @my_var => "v"
 }

Thoughts?

=end


-- 
http://bugs.ruby-lang.org/