this post was submitted on 11 May 2026
62 points (98.4% liked)

Programming

26909 readers
403 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] jtrek@startrek.website 49 points 2 days ago (5 children)

I use keyword arguments in Python to minimize this pain. Instead of


create_user("Bob", True, False)

it's


create_user(name="Bob", admin=True, send_email=False)

JavaScript makes that more cumbersome with the object thing , but it's better than nothing.

[–] eager_eagle@lemmy.world 21 points 2 days ago* (last edited 2 days ago) (2 children)

This! There's also a longstanding open issue on rust to allow a similar way to pass keyword/named arguments. IMO every modern language should have something like this. Makes all the difference when reading code.

Inlay hints from your editor are a good help, but this should be built into the language.

[–] calcopiritus@lemmy.world 8 points 1 day ago (1 children)

Not saying that named parameters are bad, but the builder pattern serves the same purpose and imo it's more ergonomic.

TrainBuilder::new()
  .with_electric_motor(true)
  .with_width(1.0)
  .build()

I don't care about the color of the train or the amount of wheels, I just want the default train with a few changed parameters.

If you do named parameters in rust, you would need to set every parameter. The only way to not set every parameter is to give a special meaning to the Default trait. But that is uncommon to happen in rust. And many structs that could easily derive Default don't.

[–] eager_eagle@lemmy.world 1 points 1 day ago

If you do named parameters in rust, you would need to set every parameter.

If that's the condition, yeah, it's bad. The good thing about how Python handles it is that they can still be mandatory or optional. And that makes it a more flexible option than the builder pattern because it applies to any function or method.

[–] FizzyOrange@programming.dev 9 points 2 days ago (1 children)

Rust doesn't need this as much because it has enums so you can just do create_user(user, Role::Admin, Notify::None).

[–] eager_eagle@lemmy.world 9 points 2 days ago (2 children)

you can have a better data structure in any language, but rarely someone will bother doing that for booleans

[–] FizzyOrange@programming.dev 1 points 1 day ago

Yeah I do wonder if we need an easier way to declare these things because programmers are lazy and even in Rust I wouldn't always bother.

You can kind of do it in Typescript with strings:

function create_user(role: "admin" | "normal")

But of course the downside is they are strings at runtime. I'm sure it's possible though.

[–] Traister101@lemmy.today 3 points 1 day ago

Right cause the boolean isn't a named type. If you have two possible states that can be represented with a boolean, or an enum of the two possible states which embeds more info into the callsite

[–] Kissaki@programming.dev 10 points 2 days ago (1 children)

C# uses CreateUser(name: "Bob", admin: true, sendEmail: false)

[–] PrinzKasper@feddit.org 1 points 1 day ago

PHP is basically identical

[–] ugo@feddit.it 6 points 2 days ago

zig uses anonymous structs for the same effect

doWork(.{
    .flurbify = true,
    .flurbification_intensity = 1001,
});
[–] riskable@programming.dev 3 points 2 days ago

Thank you for posting this comment. I came here to write the exact same thing and now I don't have to!

👍

[–] HairyHarry@lemmy.world 3 points 2 days ago

You could use jsdoc comments.