12:34:57drmeisterBike: Are we moving into a bright future of working type inference?
12:35:53drmeisterFaster code thanks to elimination of unboxing/boxing?
12:36:30Bikehopefully. the code needs some work but it seems to function fine
12:36:44drmeisterWhat is the problem of applying this to fixnums?
12:36:50Bikei did some very rough speed tests and was seeing something like 66% faster code for examples like the one i posted yesterday
12:37:09Bikejust that fixnums aren't closed. if you add two fixnums you don't necessarily get a fixnum and all that
12:37:15Bikeit doesn't make it impossible, just a little more involved
12:37:48Bikewhat i'd really like to get working is floating point comparisons inlined, because then you could do floating point arithmetic without any boxing at all, but that's going to be a bit more challenging
15:03:20drmeisterEverything is working on the buildbot again.
15:30:49Bikei think i might have slowed down the compiler a bit with how i had to rewrite representation selection. kind of hard to tell at the best of times though
15:30:55Bikemaybe if i inline fixnum arithmetic i can offset that
15:34:53drmeisteryitzi: I see the debugger symbol in jupyterlab - what sort of debugging can I do with it?