Yann Hamdaoui

After a quick search, it seems that organist is making use of `__structuredAttrs`, which only appears in the documentation from version 2.14 of Nix and onward (it's absent from the...

> Maybe also would be sensible to add std.array.at_or as it would be a mirror or std.record.get_or? @yannham? Sure, it's probably not as usefulas `get_or` but it doesn't hurt. Given...

Ah, yes, we have a test which checks all the snippets in the manual, including their output, by actually running the code and capturing the result. Which means some error...

I'm always fine with smaller changes :slightly_smiling_face: we can do `at_or` in a second row. Thanks for the addition!

After some discussions, we chose to put it in a new dedicated module `std.test`.

So, this PR was delayed for reasons that have nothing to do with the original change (mostly related to our flake being outdated because of unrelated C++ compilations errors for...

The issue is the following: In the definition of `x`, you rely on the fact that `x` is a field of a recursive record and can thus 1. Refer to...

> Somehow I have the wrong mental model that the contract Feature could work like a (OOP) class constructor, that attaching a contract to a record (acting as arguments to...

> Though I'm not following on the relation between the topic of this issue i.e. "a contract bringing variable into scope" and the let type idea. I thought that was...

Argh, we should have synced before. In fact I asked about this feature on an issue thread (https://github.com/Ethiraric/yaml-rust2/issues/27), and this was implemented in https://github.com/saphyr-rs/saphyr, which is from the same author...