Hacker News new | ask | show | jobs
by steveklabnik 2940 days ago
It was an explicit design choice.

Keyword arguments are something that we haven’t totally rejected, but many are skeptical. We’ll see!

1 comments

Skepticism towards keyword arguments is something I have trouble understanding. Is it because of some performance consideration?

Thanks for your answer!

Keyword arguments tend to lead to bloated functions that try to account for every possible situation. So they're unidiomatic when compared to C-style functions which tend to always do the same thing in the same way every time you call them.

Of course, I'm assuming you're imagining an implementation where you are allowed to omit keywords to set default values. Naturally if every argument is always required, you don't have this problem.

I mostly miss them for constructing objects with default values, yes. The alternative is the builder pattern, which involves a lot of boilerplate.
Rust has macros. No such thing as boilerplate. Only libraries that havent been written yet. :D
:)) I love macros so much