bug#79762: Guile may run stale code if source changes too quickly

Nikolaos Chatzikonstantinou <[email protected]> writes:

> This is an artificial example.  In what situation did you encounter
> this issue?  I am wondering if it is easier to fix that situation
> instead of submitting this patch.

I believe I've run in to guile running stale code more than once (after
I figured out what was going on), which is why I started looking around
for a cause, but I don't have a good idea exactly what might have been
provoking it, and it's been a while --- I just made a note to eventually
investigate.

Though I've also wondered whether loading might somehow (also) be
capable of falling back to a stale .go after a compilation error, or
similar, which could explain what I saw, and probably be less unlikely.

Thanks for the evaluation
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4