!yxFWYdmeLrdzdoIrcE:maralorn.de

nix-output-monitor

108 Members
https://github.com/maralorn/nix-output-monitor36 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
22 Nov 2024
@maralorn:maralorn.demaralorn In my mind memo basically converts "a -> b" into something like "Map a b" where the b part is lazy and all possible keys a are in the map, so that lookup again has the signature a -> b. 20:41:19
@picnoir:alternativebit.frPicnoirWorst case scenario, if I don't manage to understand how this thing works, I can rewrite this part memoization part in a more dumb-dumb explicit way.20:41:30
@picnoir:alternativebit.frPicnoirOr let you write this part :P20:42:09
@maralorn:maralorn.demaralornYeah, I am sure we can do it together.20:42:30
@maralorn:maralorn.demaralorn
In reply to @maralorn:maralorn.de
In my mind memo basically converts "a -> b" into something like "Map a b" where the b part is lazy and all possible keys a are in the map, so that lookup again has the signature a -> b.
This would be relatively easy to write down if it weren’t for the fact that Map a b is spine strict so all a actually exist in memory. That’s why that lib has another Map a b like datastructure which tries to force as little keys as possible on lookup.
20:44:46
@maralorn:maralorn.demaralornAt least that’s my understanding.20:45:07
@picnoir:alternativebit.frPicnoirAlright, doesn't seem so hard in the end.21:03:05
@picnoir:alternativebit.frPicnoirDo you have a way to test that?21:03:09
@picnoir:alternativebit.frPicnoirReworked the stdin buffering set/release.21:03:29
@picnoir:alternativebit.frPicnoirI might not have as much computer time as I originally planned this weekend in the end. But that's no a big deal, I'll have pleinty spare time next week :) 👋21:04:12
@maralorn:maralorn.demaralorn
In reply to @picnoir:alternativebit.fr
Do you have a way to test that?
I have one benchmark and we can see if it got worse, but it is not super automated.
21:05:52
24 Nov 2024
@weethet:catgirl.cloudWeetHet joined the room.11:46:15
25 Nov 2024
@nullcube:matrix.org@nullcube:matrix.org joined the room.10:04:53
@luxus:beeper.comluxus joined the room.18:06:43
26 Nov 2024
@picnoir:alternativebit.frPicnoir Ok, I spent a little bit more time digging into this memoization issue yesterday. I sadly still don't understand how we're bursting it. The print state TMVar is not updated unless we had a user interaction, in which case it'd mean we do have to compute writeStateToScreen again. 08:48:30
@picnoir:alternativebit.frPicnoirI'm maybe missing the point.08:48:44

Show newer messages


Back to Room ListRoom Version: 9