14:46:01Bujewrote out a generic function with a comple complicated methods to see how long it takes to compile - 5-6 ms with the bespoke compiler, 16-17 ms with the bclasp
14:46:16Bujebut if we cut down on startup like i've been doing that's probably fine
14:46:21Bujeperformance is a little harder to work out
14:50:28Bikeanyway maybe we can just inline the few functions used in the bclasp version and the speed difference will mostly go away and we won't have to think about how to do horrible things with arguments vaslists
15:09:22Bikedrmeister: so here's one thing - bclasp version doesn't actually use anything in fastgf.cc except cc_read_stamp, so i could just move it and then use it normally
15:09:43Bikemove it to builtins or something, i mean
15:10:23Bikewe'll also want to inline slot accessors, i just remembered, but we can probably do that similarly
15:19:43beachAm I understanding you right that you want to remove the bespoke compiler in favor of the existing bclasp compiler for discriminating functions?
15:23:51beachI am always in favor of decreasing the maintenance burden, but it is less of a problem for Clasp than for me, given that drmeister has an order of magnitude more work capacity than I do.
15:27:49Bikeyeah things will be simplified if we can just use the normal compiler.
15:28:05Bikebut the main reason is just that if we have common lisp source for discriminating functions, we can put them in fasls. that's nice.