2:29:38drmeisterI'm working on the kinematics code.
2:35:11karloszdrmeister: i think it would make sense to put it as the first optimization, right after converting to hir. that's the stage i applied the optimization to, and it should help speed up the other passes too
2:46:25DVSSAOk perfect. What exactly are our goals for the meeting so I can better prep.
2:51:47drmeisterThe goal is to get on the same page with the atom tree and fold tree.
2:52:56drmeisterWe could postpone it until I get the kinematics working - but it helps to talk about it.
2:53:23drmeisterWhen I first implemented it I made it way too complicated - I'm simplifying it now.
2:58:18DVSSASooner is probably better than later then so lets keep it at tomorrow.
3:01:18karloszBike: you mentioned that generate asts is older. does that mean at some point it will be deprecated and a switch will be made to csts+ast?
8:25:12scymtymis (will) clasp (be) using the lambda list parsing facilities of the concrete-syntax-tree library? i'm asking because i noticed a few missing/suboptimal things when switching lambda list parsing to it in my toy
12:44:07scymtymas far as can tell, concrete-syntax-tree does not check for repeated parameter names, using constants as parameter names, etc. does clasp implement its own checks for these or how does this work?