diff options
author | Profpatsch <mail@profpatsch.de> | 2021-02-06T19·31+0100 |
---|---|---|
committer | Profpatsch <mail@profpatsch.de> | 2021-02-06T19·43+0000 |
commit | 42974ddd6494097bf8a85a123b8637115977dda4 (patch) | |
tree | 00f00965ae4733fed0007f17db6208eb62c5cf99 /third_party/grpc | |
parent | 14f9a22f4641ea214af1513bc1f9ef12b1350cbe (diff) |
feat(users/Profpatsch/netencode): nest Us in U::List r/2184
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
Diffstat (limited to 'third_party/grpc')
0 files changed, 0 insertions, 0 deletions