<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdoc/src/parse2/internal_prelude.rs, branch arti-v2.3.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.3.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.3.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-03-19T10:37:47Z</updated>
<entry>
<title>tor-netdoc: Apply deferred rustfmt churn to imports</title>
<updated>2026-03-19T10:37:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-11T12:59:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9427eca66096a2a333fafb360532a3679dc52fd9'/>
<id>urn:sha1:9427eca66096a2a333fafb360532a3679dc52fd9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: parse2: Don't impl NetdocParseable for bodies of signed docs</title>
<updated>2026-03-19T10:37:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-11T12:24:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5e5dc10f0f4d477bf0e8e4d2197610c149a59541'/>
<id>urn:sha1:5e5dc10f0f4d477bf0e8e4d2197610c149a59541</id>
<content type='text'>
Such an impl is a footgun.  Explain this in docs &amp; comments.
</content>
</entry>
<entry>
<title>tor-netdoc: parse2: Move hash out of signature items</title>
<updated>2026-03-19T10:37:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-11T13:06:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aefa48e251f514a2cdbcb9e4a26292438b74af68'/>
<id>urn:sha1:aefa48e251f514a2cdbcb9e4a26292438b74af68</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>tor-netdoc: parse2: Introduce SignatureData struct</title>
<updated>2026-03-19T10:37:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T19:24:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=399c09200a008b02f4a9551fed22032feacf198d'/>
<id>urn:sha1:399c09200a008b02f4a9551fed22032feacf198d</id>
<content type='text'>
This is going to contain body information, and the hashes, too.
</content>
</entry>
<entry>
<title>tor-netdoc: NetdocParseableSignatures: Make into its own trait</title>
<updated>2026-03-19T10:37:47Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T19:08:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=785576835464aa7737e06d0088f377548df0e62b'/>
<id>urn:sha1:785576835464aa7737e06d0088f377548df0e62b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Apply rustfmt churn</title>
<updated>2026-03-03T18:57:38Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T18:57:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=96114eb9a68ca1c8062bc3f8761aee90115e003d'/>
<id>urn:sha1:96114eb9a68ca1c8062bc3f8761aee90115e003d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: parse2: Use eprint for dtrace</title>
<updated>2026-03-03T18:56:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T18:03:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=479ca8e50d8973fbf76647976aeaa37baa87c708'/>
<id>urn:sha1:479ca8e50d8973fbf76647976aeaa37baa87c708</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-netdoc: Rename *Signed to *Unverified</title>
<updated>2026-03-03T18:56:01Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T18:46:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9018c73d34ca60c5f671eeafc540446864998941'/>
<id>urn:sha1:9018c73d34ca60c5f671eeafc540446864998941</id>
<content type='text'>
This was a weird name, and while working in this area it all seemed to
make the docs strange.

Rename it.  This is quite invasive!

In theory we could have the macros generate compatibility aliases, but
that seems quite complex.
</content>
</entry>
<entry>
<title>tor-netdoc: Move NetdocSigned to signatures.rs</title>
<updated>2026-03-03T18:53:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-03-03T18:45:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a465848cbb09f602075bd6c7c3c7444d224a6f43'/>
<id>urn:sha1:a465848cbb09f602075bd6c7c3c7444d224a6f43</id>
<content type='text'>
I keep not finding it because all the other signatures stuff is in
signatures.rs.
</content>
</entry>
<entry>
<title>tor-netdoc: parse2: Provide NetdocParseable::is_structural_keyword (rustfmt)</title>
<updated>2026-01-15T12:37:09Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-01-14T18:30:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8bfd8cabd5778e622e3521d378200d54b9f9a5bf'/>
<id>urn:sha1:8bfd8cabd5778e622e3521d378200d54b9f9a5bf</id>
<content type='text'>
</content>
</entry>
</feed>
