3 ms·
Not the OP, but I'm thinking about like closures? Say you wanted to make a Node.js framework with callbacks that react to an event. The callback might be a cl
by tombert 19d ago
Not the OP, but I'm thinking about like closures?
Say you wanted to make a Node.js framework with callbacks that react to an event. The callback might be a closure that captured some of its surrounding variables. At that point, any of the captured variables are not trivially stack-allocated.
You might be able to do something similar to what Rust does with moving though.
- skew-aberration 19d agoYou could predefine your event handlers within your context, then call 'enter framework' and pass your event handlers as arguments. this is continuation passing style
- cmrx64 19d agoit is, but more specifically it’s an eliminator for a coinductive step.
- com2kid 19d agoNah we did something similar on Microsoft Band. I wrote about how - https://meanderingthoughts.hashnode.dev/cooperative-multitasking-on-microsoft-band https://meanderingthoughts.hashnode.dev/cooperative-multitas... The tldr is you had to preallocate a struct with anything you wanted captured ahead of time.
- jandrewrogers 19d agoTypically you would construct this state in statically allocated memory. A lot of systems work this way. Dynamic heap allocation isn’t the only alternative to stack allocation.