42974ddd64
Earlier we left the next level of values unencoded, since lists are just concatenated netencode values. But I noticed that you can’t write e.g. a `t_to_u` function, because only in the case of lists you need to allocate memory. Turns out that if we read the next level of values, everything is handled the same as in `Record` and things suddenly start working. We can also throw away some of the strange and ad-hoc parser helpers we needed before, `skip` and `list_take`, since now those are just normal `Vec::iter().skip()` and take. Change-Id: Ibc476e028102944a65c2b64621047086cfc09aa5 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2488 Reviewed-by: Profpatsch <mail@profpatsch.de> Tested-by: BuildkiteCI |
||
---|---|---|
.. | ||
arglib | ||
emacs-tree-sitter-move | ||
execline | ||
netencode | ||
netstring | ||
nixpkgs-rewriter | ||
writers | ||
lib.nix | ||
OWNERS | ||
read-http.nix | ||
read-http.rs | ||
rust-crates.nix | ||
tree-sitter.nix |