If you’re looking for declarations, some languages use const, let or var followed by the name of said variable. That’s a little easier to find than having a type name at the start, so I don’t think what you’re saying gives the other approach an advantage. The indentation is also more consistent with these keywords, which helps.
I realise some languages (like Python) don’t use these sorts of keywords during declaration. For those languages it could indeed be a disadvantage.
What you’re saying is more consistent, but I don’t think it’s more readable
I’m fine with let or var…if the compiler is going to infer the type thats all well and good. But it’s a replacement for the type - why would you write both? It should be either or
And if the type is being inferred, the next thing I want to know is where it came from. That tells you the type and more, I don’t want to have to see a type name that may or may not be there
Counter argument - putting the type first makes it easier to see where it is declared. Which is more important than the name or the type
If you’re looking for declarations, some languages use
const,letorvarfollowed by the name of said variable. That’s a little easier to find than having a type name at the start, so I don’t think what you’re saying gives the other approach an advantage. The indentation is also more consistent with these keywords, which helps.I realise some languages (like Python) don’t use these sorts of keywords during declaration. For those languages it could indeed be a disadvantage.
What you’re saying is more consistent, but I don’t think it’s more readable
I’m fine with let or var…if the compiler is going to infer the type thats all well and good. But it’s a replacement for the type - why would you write both? It should be either or
And if the type is being inferred, the next thing I want to know is where it came from. That tells you the type and more, I don’t want to have to see a type name that may or may not be there