freenode/#clasp - IRC Chatlog
Search
14:59:27
Colleen
Bike: drmeister said 13 hours, 18 minutes ago: I've made a mistake, satiation the way I imagined it does fully solve the dispatch problem. Instances of CL defined classes like STANDARD-GENERIC-FUNCTION have FUNCTION in their class precedence list - so the single-dispatch generic functions for FUNCTION have to handle instances of STANDARD-GENERIC-FUNCTION. It's not just C++ classes that have to respond. It looks like I'll have to put a mutex on
14:59:42
Bike
drmeister: rather than using mutices, you can just use atomics and CAS like we do for call histories
15:00:39
Bike
::notify karlosz local call idea: 1) lose local-call class 2) add slot to abstract-call that's either NIL or the FUNCTION being called 3) inline etc use that slot but leave enclose in place 4) a later, possibly client specific pass eliminates the enclose instruction if the calls don't need it