22:38:52qhongok, now my interpreter manage its own memory and can run DEAD-LOOP! for ever!
2:20:27|3b|(setf fdefinition) of inline functions seems to confuse sbcl
2:20:51|3b|The value #<SB-FORMAT::FMT-CONTROL "The result type from ~A:~% ~/SB-IMPL:PRINT-TYPE/~%conflicts with the definition's result type:~% ~/SB-IMPL:PRINT-TYPE/"> is not of type STRING when binding SB-C::FORMAT-STRING
2:21:54|3b|(very simple functions that just return a constant, which i assume is what it was trying to say didn't match)
2:32:47|3b|ACTION wonders if note-lossage works properly at all, since it seems to be declared to take a string but gets optimized to be passed a compiled format string
2:49:28|3b|presumably compiler-mumble and note-unwinnage are similarly broken, since they share the optimization and defknown