mirrors/arti.git/crates/tor-netdoc/src/parse2/multiplicity.rs, branch main mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=main 2026-05-18T15:49:06Z tor-netdoc: Document that parse2 vs encode multiplicity match req't 2026-05-18T15:49:06Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-05-18T13:57:09Z urn:sha1:e131c3bfc8b6eb51f34d64f27a86f2da4170d821 tor-netdoc: Introduce RetainedOrderVec parse/encode type 2026-04-23T15:45:52Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-04-23T12:21:02Z urn:sha1:a1f863a8651196bc34bb7ea8b24362e2e7d57927 tor-netdoc: parse2 multiplicity: Add debugging methods to traits 2026-04-13T18:38:12Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-04-13T11:45:07Z urn:sha1:1a2759e203165f26256466db3abd087badaa9a16 Fix typos 2026-03-24T16:04:08Z Tobias Stoeckmann tobias@stoeckmann.org 2026-03-24T16:04:08Z urn:sha1:1fb2b8dd4aee7c943ce90d6631be473f2a296fe6 Typos found with codespell tor-netdoc: parse2: Move hash out of signature items 2026-03-19T10:37:47Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-03-11T13:06:35Z urn:sha1:aefa48e251f514a2cdbcb9e4a26292438b74af68 During encoding, including these hashes in the signature items makes no sense. The hashes are an *input* to the signature items, but not part of them. Move the hashes out of the items. Instead, provide each signatures section type with a hash accumulator type, in which the hash(es) are stored. tor-netdoc: parse2: Provide NetdocParseable::is_structural_keyword 2026-01-15T12:37:09Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-01-12T17:42:11Z urn:sha1:3892195d3b944474f5fd73336aa213104ff71b52 Roughly as per the proposal in `doc/dev/notes/authcert-in-consensus.md`. tor-netdoc: encoding: Provide multiplicity module 2025-12-10T11:05:28Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-12-08T12:30:29Z urn:sha1:3fc25a9325703282605730b0ffa5cefe4d4f4a5a This is quite like the one for parse2, but separate for Reasons. Also add a bit of explanation to parse2's multiplicity.rs, about why there are all these different FooSetMethods traits, which the encoder doesn't need. tor-netdoc: NetdocParseable: Document that BTreeSet is allowed 2025-12-10T11:05:28Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-12-08T13:53:35Z urn:sha1:2d06bc963dfca594d0c06362e8f09bf3f0aca981 When we implemented this we documented it for ItemValueParseable but forgot to do so for NetdocParseable. Add some xrefs to the traits to try to stop similar mistakes. tor-netdoc: parse2: Combine all the multiplicity Selectors 2025-11-19T13:23:22Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-11-19T13:14:57Z urn:sha1:7df3d2f54bd6c62ac113d84f9b91880d630d63a4 There is no conflict between the different uses. Having just one type makes things simpler. tor-netdoc: parse2: Move multiplicity docs examples into Methods traits 2025-11-19T13:21:55Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-11-19T13:06:46Z urn:sha1:399d47bb7bd10e9269d2078628f98699bd78f66f We're going to combine all the Selector types, so it won't be able to have these. The diff is misleading: it's docs for the Selectors that's moving.