13:49:10beachI was a bit surprised that you didn't hoist trivial constants.
13:49:32beachBut it doesn't matter, since I will introduce others later, so I need to host those anyway.
14:41:19beachWhen I hoist constants, I would like to stick them in a slot in the TOP-LEVEL-ENTER-INSTRUCTION.
14:42:06beachBut many not all clients need such a thing.
14:42:18beachSo I'll probably just define a subclass.
14:44:19heisigbeach: You mean during HIR, right? Because AST hoisting simply turns constants into top level forms.
14:44:45beachNot trivial constants, if I read your code right.
14:47:30heisigA client need not declare any constants trivial. This is an optional feature. Albeit, some trivial constants are probably needed to break circularities.
14:48:23beachWell, I think it would be silly for SICL not to define (say) a list of numbers as trivial.
14:51:39beachIt still seems silly to take apart a list of numbers and recreate it at load time when it can be created at read time.
14:52:14heisigThere are a number of problems with that. Conses can have circular structure, and any substructure can contain objects that cannot be printed readably.
14:53:14beachSure, the client-specific method on TRIVIAL-CONSTANT-P would have to test that.
15:37:23heisigMy next goal for Trucler is to introduce all the necessary augmentation functions such that native environment can be passed to CST-to-AST.
15:40:30heisigOh, neat: Once trucler-native works on all modern implementations, people can use AST walkers instead of code walkers. That could be useful.