[02:29] *** camelia left
[02:31] *** camelia joined
[03:22] *** nine left
[03:22] *** nine joined
[10:48] *** apogee_ntv left
[10:49] *** apogee_ntv joined
[13:17] *** rakkable joined
[15:31] *** apogee_ntv left
[16:59] *** apogee_ntv joined
[18:11] <ab5tract> Any measurable impact of the work saved by using żmij?

[19:51] <japhb> ab5tract: I would expect to see it show up in text serialization benchmarks, such as representing large floating point arrays in JSON, XML, or COLLADA.

[20:56] *** rakkable left
[20:56] *** rakkable joined
[23:49] <timo> after some trial and error I've now got what seems like a first working "track this object through it's history"; for any kind of object it will understand when it gets moved by the GC and go all the way back to where it was allocated, but for VMArray it will also find when the number of elements changes, or the start attribute changes, or the storage pointer gets changed

[23:58] <japhb> Oh nice timo++

[23:58] <timo> this of course only works inside an rr replay

[23:58] <timo> otherwise you can't go backwards through execution

[23:59] <timo> I also want something like pernosco's "see stdout or stderr and click on a character to jump to when it was outputted"