// TODO: Insert some catchy introduction sentence linking to the previous update
@pamplemousse kept working on the fuzzing of the Nix evaluator. You can read more about it here, but the gist of it is that we’re slowly approaching the point where we can run some full-scale fuzzing sessions.
@regnat wrote and @edolstra reviewed a number of fixes for some issues on the 2.4 milestone (3516, 3774, 3944 and 3503 which are merged, as well as #4548, #3888 and #4507 which are still WIP).
There’s still a bunch of issues in the associated milestone, but it’s shrinking quickly, and only a handful of them are really critical anymore.
- Thanks to the knowledge accumulated during his past work on the Nix evaluator (4154 and 4355), @infinisil started a Wiki page on the Nix evaluaton performance and the tradeofs to have in mind when writing performance-sensitive (!) Nix code.
And that’s all, folks