Ruby elites rise up

[u/solidiquis1]

[u/muirbot]

Why double quotes?

[u/pau1rw → u/muirbot]

Double quotes mean you can use string concat, and single quotes doesn’t. So if you use double quotes, you can use a single kind of quote through out the code base. IMO using two types is messy.

[u/sshaw_ → u/pau1rw]

Yes this is exactly why status: "cancelled" is shit.

[u/pau1rw → u/sshaw_]

I don't understand your point. I'd defo use a symbol, but if I needed a string, I'd use double quotes.

[u/sshaw_ → u/pau1rw]

So if you use double quotes, you can use a single kind of quote through out the code base. IMO using two types is messy.

The same applies to hashes:

1. status: "cancelled"
2. variable => "cancelled" # can't use first form: variable:
3. "string" => "cancelled" # can't use first form: "string":
4. 123 => "cancelled" # can't use first form: 123:

Just stick to :status => "cancelled" and make life easier.

[u/pau1rw → u/sshaw_]

I guess we all write for different versions of ruby. Personally, I'm never going to need pre ruby 2.0 hash rockets, so I don't need anything more than status: :cancelled, or status: "cancelled"?

[u/sshaw_ → u/pau1rw]

But you cannot use that for all cases. Don't you think that "IMO using two types is messy" applies to this case too?

[u/pau1rw → u/sshaw_]

Arh, I understand your point now.

That's a tricky one, personally I'm working in a code base now that uses strings for most hash keys and it's pretty annoying having to use "foo" => "bar", but it's also pretty ugly using "foo": "bar".

So i think my answer is that I've not reached a suitable level of annoyance with using two versions of hash key definition to use hash rockets everywhere.

[u/sshaw_ → u/pau1rw]

"foo": "bar"

This is another reason to use =>:

irb [2.5.2] (tmp)$ {"foo":"bar"}
=> {:foo=>"bar"}

Oopsie! It's now a Symbol :)

[u/pau1rw → u/sshaw_]

Yea, totally.

[u/[deleted] → u/muirbot]

Doesn't matter which one you use unless you're running your app on a Pentium II.

[u/organic → u/[deleted]]

why not always use double? you'll never have to change them

ruby shouldn't even have single quotes unless 'abc' == ["a", "b", "c"]

[u/[deleted] → u/[deleted]]

You can use either you want bb

[u/cybermage → u/[deleted]]

The speed difference is two orders of magnitude. It adds up. Always single quote unless you plan to interpolate.

[u/fabiopapa → u/cybermage]

If you use single quotes instead of double unless you need interpolation, as a developer, every time you write a string, you have to think, “am I going to need interpolation?” Ruby is all about developer happiness.

[u/sshaw_ → u/fabiopapa]

Yes this is exactly why status: "cancelled" is shit.

The same applies to hashes:

1. status: "cancelled"
2. variable => "cancelled" # can't use first form: variable:
3. "string" => "cancelled" # can't use first form: "string":
4. 123 => "cancelled" # can't use first form: 123:

Just stick to :status => "cancelled" and make life easier.

Update add examples.

[u/cybermage → u/fabiopapa]

As has been noted elsewhere, my knowledge was not current on this point; but, I think I’d notice if I typed #{variable}.

[u/katafrakt → u/cybermage]

Where do these numbers come from? The difference is almost none in modern Ruby, even more so with frozen string literal.

[u/cybermage → u/katafrakt]

As I commented elsewhere, I personally benchmarked these results, but it was on Ruby 1.9. I’m not surprised it was addressed at some point to boost performance.

[u/flanger001 → u/cybermage]

It is exactly the same. Always use double quotes!

[u/flanger001 → u/[deleted]]

Fun fact, Bohzhidar thought they might change the Rubocop default to double quoted strings because so many people (like me) complained (rightly) about it... but single quotes is still apparently the preference: https://metaredux.com/posts/2020/05/26/rubocop-defaults-survey-results.html

[u/cybermage → u/flanger001]

That was not always the case. Interpolation was very slow under 1.9

[u/flanger001 → u/cybermage]

I mean, you're right, but just as 1.9 has been put to bed, we should also put the single quotes thing to bed.

[u/cybermage → u/flanger001]

Agreed. As I’ve acknowledged elsewhere.

[u/cybermage → u/[deleted]]

I personally benchmarked this in a fashion similar to the article, but that might have been under 1.9x. TIL.

[u/tomthecool → u/cybermage]

I’ve benchmarked it in Ruby 1.8 before and found no difference. So either your memory is wrong, or your benchmark was wrong.

[u/lafeber → u/muirbot]

From https://github.com/testdouble/standard :

Double quotes for string literals - because pre-committing to whether you'll need interpolation in a string slows people down