Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Even though it's common, I don't like the explicit "case" syntax. It's fairly obvious when you're entering a discriminator. Given that, it's just ceremony. I don't find value in the added explicitness, preferring instead an ocaml-style approach that minimizes tedious symbolic prefixing.
Ex: Give keyword match, I know I can expect the next child indented case to be a case statement, if it's not, compiler error.
That said, I fully support adding pattern matching to basically everything.
vane76285dLooks like switch case.
Still waiting for do while loop 😂
I think this is quite fitting:
Like, fuck, shit like numba should be integrated into python.
Pip is so broken.
But oh, I have an idea, let's implement a half baked, slow as shit match statement that looks like a switch ! Who cares if a usage takes 1 full second to get printed.
vintprox6505dI don't want to be rude, but they'd better propose common comments and annotations syntax, because I can't seem to make simple comment appear for variable and it's a pain in ass to constantly switch between files just to see if there is any comment above class property. Though with functions it seems to work all well if I place comment in its body...
SomeNone7943dSo if I read correctly, this is a statement, not an expression?
Fuck that, go back to the cave whence you came.