| 22 Nov 2024 |
 Picnoir | * I have to confess I don't know how to fix the memoization issue rn. I have to figure out how this memoization thing is working. The documentation of the library is terse and is pointing to dead links, rough start :D | 20:32:06 |
 maralorn | In reply to @picnoir:alternativebit.fr
Meh, nevermind, I can append that in my wrapper. Let's change that. I guess I can live with both solutions. | 20:33:26 |
| maralorn | In reply to @picnoir:alternativebit.fr
I have to confess I don't know how to fix the memoization issue rn. I have to figure out how this memoization thing is working. The documentation of the library is terse and is pointing to dead links, rough start :D Yeah, it is a bit gnarly. | 20:33:55 |
| maralorn | I see about two solutions: 1. Only apply print state when the state itself changes. 2. memoize the Printstate. Both should be doable. | 20:34:44 |
| maralorn | * I see about two solutions: 1. Only apply new print state when the state itself changes. 2. memoize the Printstate. Both should be doable. | 20:34:58 |
| maralorn | i.e. its fine when a print state change invalidates memoisation, we just don’t want it reapplied everytime. | 20:35:50 |
| Picnoir | Right | 20:40:43 |
