freenode/#clasp - IRC Chatlog
Search
19:42:35
Bike
yeah, well the underlying problem was (subtypep 'core:complex-vector-t '(vector t)) returned nil
19:44:05
drmeister
I hit a problem and map was in the backtrace yesterday - it may not be the same problem.
19:44:29
Bike
the way to hit it would probably be something like what mcclim was doing, (map (class-of some-complex-vector-t) ...)
19:45:44
Bike
that and the cltl2 interface are the only things i've done there in two weeks, so it's probably fine
19:45:57
Bike
i've mostly been doing another compiler overhaul thing in another branch, so it shouldn't cause problems
19:47:48
drmeister
I think we are the only implementation that takes advantage of slime code that scans for an available port.
19:48:06
Bike
i mean, like i'm wondering whether that should be done around the slime-connect call or something
19:49:34
drmeister
It would require changes to the elisp code to do anything more sophisticated I mean.
19:50:24
Bike
in case slime uses create-socket more generally, i guess, like in cotnexts you wouldn't want to restart so much
19:51:59
drmeister
I don't know - I haven't considered the greater good here. I have just want jupyterlab/cando to stop crashing because one jupyterlab accidentally tries to use the same port as another one is already using.