ASDF uses CHANGE-CLASS because (1) it caches a system's identity before it's defined (2) re-loading can cause changehttps://twitter.com/juhosnellman/status/625712153891315713 …
-
-
As usual, CL's "let's side-effect the one true (local) world" semantics feels low-level. Yet so much higher-level than cult-of-dead systems.
-
Also, the live system of the future must manage distributed state, not just local state. Thus minimize side-effects, emphasize monotonicity.
End of conversation
New conversation -
-
-
CL code upgrade issues: no transactions; unclear inline (default) function call semantics; no U-I-F-R-C for stack frames.
-
code-upgrade friendly: transactions; virtualization; syntax distinction b/w static&dynamic calls (like erlang). U-I-F-R-C for stack frames?
End of conversation
New conversation -
-
-
@fare what’s U-I-F-R-C? Google not helping. -
@rentzsch If you scroll up the conversation, you'll see U-I-F-R-C is UPDATE-INSTANCE-FOR-REDEFINED-CLASS. http://malisper.me/2015/07/22/debugging-lisp-part-3-redefining-classes/ … - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.