@dthompson Hi Dave!
Last time you've mentioned that when you do interactive development, you need to wrap functions with trampoline call to always get a fresh defenition of the function.
Can you share the implementation of trampoline, please?
@dthompson Hi Dave! Can you share the implementation of trampoline, please? 4 comments
@daviwil I think you are right, and it's more an a problem of event loops, when the code already obtained a value of a variable and use it on each iteration. Like a handler example mentioned by @krevedkokun @abcdw @krevedkokun @dthompson yeah, that one definitely makes sense, and @krevedkokun's solution is also what I do in other cases like game engine loops @abcdw @dthompson when I've played with guile http server I just wrapped handler with lambda, so it would call last version of handler function each time |
@abcdw @dthompson I'm surprised this is necessary, I thought that Guile modules export "variables" that are boxes for the exported values so that they can be replaced on a new eval