▲ | Asooka 3 days ago | |||||||||||||||||||||||||
Code with types on the right like this makes me very sad
Types are a lot more ergonomic on the left - the return type of a function and the type of a variable are very important for understanding and skimming code. When the return type is on the right, it is physically very far from the name of the object and I have to scan the entire line with my eyes to get the same amount of information I would get by just looking at the left column and scrolling down if it were on the left. I am pretty sure in another 20 years types on the right will be regarded as one of the ergonomic fails of current language design. At least, if have to do this, put the type right under the object name, like so:
Future readers will thank you. | ||||||||||||||||||||||||||
▲ | 3836293648 3 days ago | parent | next [-] | |||||||||||||||||||||||||
Types are only nicer on the left when it isn't also annotated with all the other static constexpr [[nodiscard]] nonsense. And left types are actually greppable seperately from variable declarations. Having both left and right types is stupid, but as a whole right types are easier to deal with | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | PittleyDunkin 3 days ago | parent | prev | next [-] | |||||||||||||||||||||||||
I cannot disagree more strongly. Putting the name of the function (or method) in the middle of the declaration drastically lowers readability. C-style type declarations were always the most painful part of reading C. | ||||||||||||||||||||||||||
▲ | binary132 3 days ago | parent | prev | next [-] | |||||||||||||||||||||||||
FWIW I completely agree, I think -> rt is a very silly idiom in declarations. It’s fine and useful for lambdas. | ||||||||||||||||||||||||||
▲ | bigstrat2003 3 days ago | parent | prev [-] | |||||||||||||||||||||||||
No they won't. Your example is way more unpleasant to read. |