Steve Klabnik recently wrote about named arguments, optional arguments, default arguments, function overloading, and why most of that design space has historically made him nervous in Rust.
I agree with Steve.
In fact, I think I agree slightly more s…
In Python land you end up with functions with 30 arguments and when they want to pass them anywhere they give up and use kwargs which 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.
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.md that 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.)
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.