News for hackers. Stuff that matters.
Re:Writing Python like it's Rust by dgan on Sunday May 21, 2023 @10:44AM (#36021433)
> it never comes up because when you know what domain you're working in it's always immediately obvious what types the arguments are.

Oh this one is hilariously wrong. Is it InvoiceLine that we are getting here? Or Maybe LineInvoice? Nope those aren't the same. But the only argument is called «line». How shameful. Much sadness. Better add a print statement, push a new build and comeback in twenty minutes

Re:Writing Python like it's Rust by okasaki on Sunday May 21, 2023 @11:23AM (#36021891)
It sounds like the codebase sucks or you haven't taken enough time to understand it.
Re:Writing Python like it's Rust by dgan on Sunday May 21, 2023 @11:54AM (#36022205)
That's beside the point. Those types ("types" you see? hehe) go against your argument "it's obvious from the context", because now it becomes "it's obvious from the context if you are lucky enough that your codebase doesn't suck or you spent 'enough' time figuring it out"
Re:Writing Python like it's Rust by esafak on Sunday May 21, 2023 @04:10PM (#36024281)
Suppose it sucks, and you are expected to contribute it already. Welcome to the real world?