this post was submitted on 09 May 2024
440 points (92.1% liked)
Programmer Humor
32032 readers
1249 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why have an async block spanning the whole function when you can mark the function as async? That's 1 less level of indentation. Also, this quite is unusable for rust. A single match statement inside a function inside an impl is already 4 levels of indentation.
How about this?
I had some luck applying this to
match
statements. My example:Is this acceptable, at least compared to the original
switch
statement idea?i personally find this a lot less readable than the
switch
example. thecase
keywords at the start of the line quickly signify its meaning, unlike with=>
after the pattern. though i dont speak for everybody.How about this one? it more closely mirrors the switch example:
How about this other one? it goes as far as cloning the switch example's indentation:
the problem is that, while skimming the start of each lines, nothing about
'G' | 'g'
tells me that its a branch. i need to spend more time parsing it. mind you, this may simply be a problem with rust's syntax, not just ur formatting.