22:00:20Bikedrmeister: a hinta bout what "The dispatch function has two selectors with different outcomes" would be helpful, because i'm pretty clueless
22:11:41drmeisterI just got off the plane and I'm heading downtown for a late meeting.
22:13:52drmeistertwo selectors with different outcomes is bad - I think it means the generic function dispatch is building the dispatch tree and it got to a point where it was going to add an outcome and there was one already there.
22:14:15drmeisterOh - you aren't online - I'll catch you later.
22:15:37drmeisterBut I think it means that the call history has two entries with the same key but different outcomes (really bad) - or the same outcome (and then the two entries are only redundant - but still bad). The keys in the call history should always be unique.
22:17:52drmeister::notify Bike - I just put some stuff in the log for you.
22:17:52Colleendrmeister: Got it. I'll let Bike know as soon as possible.
22:21:08drmeisterWhile I was on the plane I started working on getting Maxima to work in Clasp - wow - it goes to town on symbol properties.
23:09:30Bikethe underlying issue is probably that i messed up whatever magical process gives boot classes stamps
23:09:30ColleenBike: drmeister said 51 minutes, 38 seconds ago: - I just put some stuff in the log for you.
23:13:14Bikeand i really have not got any idea about that
23:14:54Bikei know standard-class exists in the interpreter somehow
23:18:38drmeisterWe’ll fix it. It’s new and not too complicated