There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

lseif ,

more practical than goto

starman ,
@starman@programming.dev avatar

Looks like C# 12 interceptors:


<span style="color:#323232;">[InterceptsLocation(@"C:testappProgram.cs", line: 4, column: 5)]
</span>

I know it looks awful, but it’s not intended for direct use, but rather for source generators for native ahead of time compilation.

andrewlock.net/exploring-the-dotnet-8-preview-cha…

Thcdenton ,

https://lemmy.world/pictrs/image/fb2e1a6f-8590-4af9-b610-e02e44945231.gif

umbrella ,
@umbrella@lemmy.ml avatar

am i the only dumb fuck here who unironically likes this?

would make goto type situations much more usable

MindTraveller ,

It’s basically a simpler version of a callback

Cethin ,

I don’t see any case where this is better than a goto. A goto you can read progressively though. A comefrom you’d see written then have to track to that piece of code and remember there’s a potential hidden branch there.

mossy_ ,

Guy who worked at my place before me kept using these and GOTO statements all over the place.

His name? Cotton-eyed Joe

match ,
@match@pawb.social avatar

Reference to Cottoneyed Joe considered harmful

mossy_ ,

I almost spat out my drink when I saw this

hakunawazo ,

Thanks for the catchy tune, now the song sticks in my mind again. Last time was long time ago. :)

lseif ,

where did you COMEFROM where did you GO…TO

match ,
@match@pawb.social avatar

where did you COMEFROM, cottonEyedJoe2

neo ,

COMEFROM is my go to function;

Sonotsugipaa ,
@Sonotsugipaa@lemmy.dbzer0.com avatar

Wh… what do you mean, “originally as a joke”?

jbk ,

til

MadMadBunny ,

You’re gonna love HCF then!

s12 ,

PLEASE COMEFROM 🏷

RiikkaTheIcePrincess ,
@RiikkaTheIcePrincess@pawb.social avatar

Aaahhh, this is horrifying! You’ve ruined my breakfast 🙀

schnurrito ,

TBH I fail to see the significant difference between this and a function declaration.

sxan ,
@sxan@midwest.social avatar

Doesn’t it steal control flow? More like a break point, except you define where execution continues.

I wonder if it’s a compile error to have multiple conflicting COMEFROM statements, or if it’s random, kind of like Go’s select statement.

How awesome would it be to be able to steal the execution stack from arbitrary code; how much more awesome if it was indeterminate which of multiple conflicting COMEFROM frames received control! And if it included a state closure from the stolen frame?

Now I want this.

davidgro ,

I wonder if it’s a compile error to have multiple conflicting COMEFROM statements

I think there’s at least one INTERCAL implementation where that’s how you start multi-threading

palordrolap ,

I'd say it's more like setting up a handler for a callback, signal, interrupt or something along those lines.

Function declarations by themselves don't usually do that. Something else has to tell the system to run that function whenever the correct state occurs.

That doesn't account for unconditional come-froms.¸but I expect there'd have to be a label at the end of some code somewhere that would give a hint about shenanigans yet to occur. Frankly that'd be worse than a goto, but then, we knew that already.

polonius-rex ,

it's semantic

at the end of the day everything boils down to sequence and branchifs

magic_lobster_party , 
print(A)
print(B)
hello: print(C)
print(D)
print(E)
comefrom hello
print(F)

This will print A, B, C and then F. D and E will be skipped because of the comefrom.

sudo ,

Its like if subroutine bar could say its going to execute at line N of routine foo. But if you were just reading foo then you’d have no clue that it would happen.

You can simulate this effect with bad inheritance patterns.

Cethin ,

A function will be called by code and go to that point in code. To implement functions, you store necessary things to memory and goto the function definition. To implement that with comefrom you’d have to have a list of all the places that need to call the function as comefroms before the function definition. It’d be a mess to read. We almost never care where we are coming from. We care where we’re going to. We want to say “call function foo” not “foo takes control at line x.”

rand_alpha19 ,

That sounds like a fucking nightmare. I had to troubleshoot poorly-written-yet-somehow-functional GOTOs a lot when I was a BAS technician and that's annoying enough.

pro3757 ,

It’s in Intercal, a joke language from '70s. Mark Rendle describes it here in his talk at NDC. This whole talk is ridiculous btw.

frezik ,

This is the same language where you have to say PLEASE sometimes or it won’t compile. But if you say PLEASE too much, the compiler will think you’re pandering and also refuse to compile. The range between too polite and not polite enough is not specified and varies by implementation.

Whelks_chance ,

I love how arbitrary, cultural and opinionated that must be to work with. You’d learn something about the implimenter of the compiler by using it for a while.

c0smokram3r ,
@c0smokram3r@midwest.social avatar

This is hilarious!

onlinepersona ,

I honestly thought C++ (aka dumping ground of programming concepts) would implement this for “completeness”.

Anti Commercial-AI license

NeatNit ,

They should add it in C++26

uis ,

C++60

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •