104
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 May 2024
104 points (97.3% liked)
Programming
17314 readers
301 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
TIL that C# and Java have a goto statement.
Forget about goto, the latest version of C# introduced what's essentially comefrom.
Please don't link to medium articles. That page is terrible to visit.
Looks fine on Firefox on Android with uBlock Origin. 🤷♂️
I'm running exactly the same and it doesn't look fine on my end.
Huh. Maybe it's NoScript, then.
Could be. I'm getting forced to make an account and such. That's why I hate medium.
To be fair,
await
is a bit more likecomefrom
, and it's been around for a few releases now.async/await was introduced in version 4.5, released 2012. More than a few releases at this point!
How is
await
likecomefrom
, any more than threading is likecomefrom
? The variable context is preserved and you have no control over what is executed before theawait
returns.What...? That is a terrible idea.
It's scary as fuck, yeah, but, to be fair, it's only intended to be used by code generators, and it's quite awkward to use outside of them.
Java doesn't. Well, it's a reserved keyword but it's not implemented.
Yeah but we got labels with continue and break, so we can pseudo goto.
Following that logic
if
,else
andwhile
are also "pseudo goto" statements.There's nothing wrong with conditional jumps - we couldn't program without them. The problem with goto specifically is that you can goto "anywhere".
If pretty much gets compiled to a goto statement. Well more a jumpif but same principle
In C# at least,
goto
can take you between case labels in a switch statement (rather than using fallthrough), which I don't view as being nearly as bad. For example, you can dogoto case 1
orgoto default
to jump to another case.The only other use of
goto
I find remotely tolerable is when paired with a labelled loop statement (like putting a label right before afor
loop), but honestly Rust handles that far better with labelled loops (and labelled block expressions).I've programmed C# for nearly 15 years, and have used
goto
twice . Once to simplify an early break from a nested loop, essentially a nestedcontinue
. The second was to refactor a giant switch statement in a parser, essentially removing convolutedwhile
loops, and just did agoto
the start.It's one of those things that almost should never be used, but the times it's been needed, it removed a lot of silliness.