3 ms·

so you can place your stack pointer back in the frame that you returned from earlier? that's probably the point at which they stopped understanding continuation

so you can place your stack pointer back in the frame that you returned from earlier? that's probably the point at which they stopped understanding continuations before even starting.

cyco130 2y ago
That’s the tricky part. There’s no stack anymore. Activation records of functions are heap-allocated and can stick around as long as necessary.
- fc417fc802 2y ago
  To be fair it's still a stack (the data structure). It just isn't contiguous in memory anymore. Of course modern LLVM already breaks it up into chunks anyway (given certain flags at least) so it likely isn't contiguous regardless.
- bryanrasmussen 2y ago
  I was explaining the joke? Since the person I was replying to seemed to wonder if it was really a joke, whereas for me, structurally it was obviously a joke.