You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the source of select-module, but still can't see why this happens. Is the local scope somehow attached to the module? And when we change the module, the scope is gone?
I have compared the bytecode for (select-module x) to the bytecode for the first expression (above):
This second one ends with local-ref0 (before the leave-let), so it "should" have returned the value of a... unless this local-ref0 actually depends on the current module. (?)
The text was updated successfully, but these errors were encountered:
But that didn't work for a couple of reasons (including the fact that I can't seem to guarantee that the current-module symbol has the binding from the SCHEME module)
When
select-module
is used inside aLET
, the result seems a bit confusing...I have read the source of
select-module
, but still can't see why this happens. Is the local scope somehow attached to the module? And when we change the module, the scope is gone?I have compared the bytecode for
(select-module x)
to the bytecode for the first expression (above):This second one ends with
local-ref0
(before theleave-let
), so it "should" have returned the value ofa
... unless thislocal-ref0
actually depends on the current module. (?)The text was updated successfully, but these errors were encountered: