49
We Have Named Arguments at Home
(corrode.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Sep 2026
49 points (100.0% liked)
Rust
8328 readers
18 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 3 years ago
MODERATORS
I agree - Structs are kind of a nicer solution here. Especially because it's pretty common to pass a whole set of options through the call stack.
In Python land you end up with functions with 30 arguments and when they want to pass them anywhere they give up and use
kwargswhich are completely awful and should almost never be used.Unpack[T]exists, but nobody uses it sadly. Also, it's probably better to just use a dataclass or something instead anyway, but nobody does.We are migrating to this (https://scverse.org/)
But that's mostly because yours truly keeps pushing API design improvements
Their docs page just flat out doesn't work on mobile, but based on the high level descriptions of the packages, these look like something I'd install on a project without asking and write in the
AGENTS.mdthat it's forbidden from using the more popular libraries in favor of those. (Our DS people, in general, can't and won't write code for shit, so it's the only way to get them to use a new library.)I think we helped improve that in our field since as I said, I've been making pleasant APIs for like 8 years there. But I know the struggle.