Make `{"foo": 1}` also be a named tuple #2795

asterite · 2016-06-10T20:11:29Z

This makes "foo bar": 1 (string literal, colon, expression) mean a named tuple literal everywhere now, and only => can be used for a hash literal.

The places where this is applicable is:

Named tuples: {"foo bar": 1}
Named tuple types: x : {"foo bar": Int32}
NamedTuple instantiation: NamedTuple("foo bar": Int32)
Calls: foo bar: 1, "baz qux": 3

I tried using this new syntax in html_builder and it worked well:

require "./src/html_builder"

string =
  HTML.build do
    html do
      body do
        a(href: "http://crystal-lang.org", "data-awesome": "true") do
          text "crystal is awesome"
        end
      end
    end
  end

puts string # => "<html><body><a href="http://crystal-lang.org" data-awesome="true">crystal is awesome</a></body></html>"

This is a breaking change, but it makes things more consistent, and allows things like the above.

Make {"foo": 1} also be a named tuple. Fixes #2631

c21ac49

asterite merged commit 3acaca7 into master Jun 10, 2016

jhass added the topic:compiler label Jun 11, 2016

asterite deleted the feature/named_argument_string branch June 13, 2016 15:28

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Make `{"foo": 1}` also be a named tuple #2795

Make `{"foo": 1}` also be a named tuple #2795

asterite commented Jun 10, 2016

Make {"foo": 1} also be a named tuple #2795

Make {"foo": 1} also be a named tuple #2795

Conversation

asterite commented Jun 10, 2016

Make `{"foo": 1}` also be a named tuple #2795

Make `{"foo": 1}` also be a named tuple #2795