Brooke Kuhlmann

Interesting, I never use parentheses in #ruby method definitions either (unless required for correct syntax parsing situations): https://dev.to/ko1/am-i-the-only-one-who-doesnt-put-parentheses-around-the-parameters-in-ruby-method-definitions-136c

This was one of many reasons I got into Ruby nearly ~18 years ago because I love you can avoid unnecessary syntax and ceremony. This is also the default setting in the Caliber gem: https://alchemists.io/projects/caliber

Am I the only one who doesn't put parentheses around the parameters in Ruby method definitions?

I'm Koichi, a Ruby interpreter developer in the Technology Division at STORES, Inc. And I'm looking...

DEV Community
Apr 15, 2024 at 6:48pmWeb
Show threadSeb WilgoszApr 15, 2024

@bkuhlmann I do use them in method calls, and I use them in RSpec, when I want to keep lines readable. Only after a few years of writing RSpec tests I've realised that `eq` is an argument, of `to`:

`expect(...).to(eq(...))`

Show threadBrooke KuhlmannApr 15, 2024

@swilgosz Ha, yeah, that's too many parenthesis for my taste. 😅

I like letting Ruby breath but eye of the beholder I guess.

Show threadPaul Sadauskas ✊ ResistApr 16, 2024
@bkuhlmann I use them always, because they’re required when a method has keyword args. I personally find the consistency to be less jarring than the extra characters.
Show threadBrooke KuhlmannApr 16, 2024
@Paul Yeah, we've talked about this before. These days, with RuboCop, you can keep either style consistent so isn't as big a deal as it once was.