Robert Hensing
Robert Hensing
Thank you @pennae
This seems more productive than [what I've been up to with a self-documenting codec abstraction](https://github.com/NixOS/nix/pull/9273), which may be too ambitious for something in C++.
Lowdown represents one local optimum, where it's responsible for the whole pipeline. This is insufficient, as described by tribals just now. Another optimum is one where we have - A...
For yet another optimum, we could consider minimizing the documentation related code in Nix, and generate the documentation as well as some code from a single source that isn't C++....
The Nix ecosystem has by and large switch to markdown in order to make writing easier, reasoning that lowering the contribution threshold leads to more end user improvements than fancy...
`:` looking like `i` is clever. Still not a fan of "just" claiming a drive. This could be a huge blocker in established environments. Can a network drive symlink to...
The FUSE idea is interesting, but I would consider it to be a separate set of features.
> Would the built-in fetchers still be executed "client-side" or by the builders? Yes, I would like the client to "join" the builders, although this is not the only way...
Also worth considering is a primop to explicitly defer the fetching to a derivation. This will be a more natural solution after the following changes: - Make `fetchTree` return a...
@yajo Thank you. This was taken into account: > When scheduling the derivations, request for the Nix _client_ to perform `addToStore` instead of scheduling an actual derivation build. "Nix client"...