From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 1B31519E0026 for ; Mon, 28 Dec 2015 11:57:43 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 7D277B5D874 for ; Mon, 28 Dec 2015 12:30:17 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id D290C18CC7E7 for ; Mon, 28 Dec 2015 12:30:17 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 12C861204DC; Mon, 28 Dec 2015 12:30:15 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o2.heroku.sendgrid.net (o2.heroku.sendgrid.net [67.228.50.55]) by neon.ruby-lang.org (Postfix) with ESMTPS id 29A8D12048C for ; Mon, 28 Dec 2015 12:30:10 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=RurNSyTziJo5hx7JMv5Llhf5/gw=; b=Id/NyAckHOJSd+mylh lLm+aw7e+zcLP4w7brr5DXptWH4cIvi6cZCs29UbEbwoYP+4VwTZCaCAVahtTGyi qX8hwhJwdHzFuoNYjUNGyacRiviQDEzcmbZcnXrLk4fgIFgQjJ/L1iA+CxExrMeJ saeswRbSJk2O6aG0UbTXBq5iE= Received: by filter0803p1mdw1.sendgrid.net with SMTP id filter0803p1mdw1.1943.5680ACBC22 2015-12-28 03:30:04.677703361 +0000 UTC Received: from herokuapp.com (ec2-54-158-90-62.compute-1.amazonaws.com [54.158.90.62]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id tiSHSdODRnCOzXX1PAr3Bg Mon, 28 Dec 2015 03:30:04.637 +0000 (UTC) Date: Mon, 28 Dec 2015 03:30:04 +0000 From: hcatlin@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 47136 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11882 X-Redmine-Issue-Author: hcatlin X-Redmine-Issue-Assignee: matz X-Redmine-Sender: hcatlin X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS5SWYzFHqW6qcIA94kBLJe4Vnys9UwCi1jb5r 5RbsNIUBcePnOif4sXgzLaa0q+OofTWynk4AWXijQqbRIzuGTqhqnYPbfpC57N4Ffs5tTc6QF2X9VL EtfQ4b1txUfXw87aNsf9egwHwHAqqznicFhV X-ML-Name: ruby-core X-Mail-Count: 72536 Subject: [ruby-core:72536] [Ruby trunk - Feature #11882] Map or NamedMap X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11882 has been updated by Hampton Catlin. That's such a kind of.... odd opinion to me. I've been doing ruby for 10 years, and I still have to write fairly obvious handling code when building programming interfaces and libraries... over and over again. I guess I just see 95% of Hash usage being made up of instances where symbols and strings are treated equally, and compensating code is required at every step to ensure that. I find it odd that this is considered an edge-case. ---------------------------------------- Feature #11882: Map or NamedMap https://bugs.ruby-lang.org/issues/11882#change-55801 * Author: Hampton Catlin * Status: Open * Priority: Normal * Assignee: Yukihiro Matsumoto ---------------------------------------- Hash is one of the best features of Ruby. I remember being so pleased when I first learned Ruby to find out that *anything* could be a key and that you could do some really clever things with scripts, if you key of non-traditional elements. However, like many people, 10 years into using Ruby, I still am writing code to cast around symbols to strings and strings to symbols, just to use Hash as a more traditional dictionary, keyed with string-like values. And, explaining to a junior programmers why they broke the code by using a key of a different type... it's not the most elegant thing to have to explain over and over. Several proposals exist for how to deal with this, and all have been rejected... however it doesn't seem like it's for essential reasons, more technical or syntactic issues. Coming up with syntax is something I quite enjoy (Sass/Haml), so I thought I'd make a pitch for it. Requirements: 1) Doesn't break existing code 2) Doesn't totally destroy the parser 3) Seems simple to differentiate 4) Clear upgrade path My proposal is to introduce an entirely different type of Hash, called a Map (or NamedMap, if that's too ambiguous), that requires a string-like key. There are no other types of keys allowed on this Hash, other than either strings or symbols. Internally, each key would be considered a symbol only. ~~~ map = Map.new(a: 2, b: 3) map["a"] #=> 2 map[:a] #=> 2 ~~~ Already, we're better than HashWithIndifferentAccess, as it's clearly a bit easier to type. ;) What about a literal syntax? ~~~ map = {{a: 2}} empty_map = {{}} ~~~ As far as I can tell in the Ruby-syntax style, this should be pretty easy to distinguish syntactically from both a regular hash literal and a block. Further, as almost every method's option hash is string-keyed, you could easily define this. ~~~ def my _method(arg1, options = {{}}) end ~~~ Immediately, you could deal with your options hash, and not have to stress about if the end user has passed in strings or symbols into the options. It would be trivial to create a Map polyfill for most libraries to start using the non-literal version right away, as it would basically be HashWithIndifferentAccess, except we need to guarantee that the keys are string-like. So, to sum up, we avoid the 'breaking other people's existing code' by introducing a new data-type, the literal syntax (I think) should be fairly easy to implement, and it makes a very natural keyed data object (e.g. Javascript Objects) and brings that to Ruby. -- https://bugs.ruby-lang.org/