| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
This lets us skip fields which have the default values.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Ie for "arguments" that don't actually appear.
|
| |\
| |
| |
| |
| | |
tor-netdoc: Three fixes to parsing and encoding
See merge request tpo/core/arti!3862
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
| |
The `doctype_for_error` attribute needs immediate adjustment, because
a string expression value is expected. With `quoted retain`, that
would be re-interpreted, silently. This kind of thing is why
`quoted rigorous` exists.
So change its docs and the one use site.
The macros' docs, and the other calls ites, we'll deal with shortly.
|
| | |
|
| |
|
|
|
| |
We mustn't use selector.selector() because that's for multiplicity,
not optionality. In pracctice, it goes wrong with Vec<u8>.
|
| | |
|
| |
|
|
| |
This was a c&p error, I think.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
With the introduction of the derives for document encoding, we now
have a trait ItemObjectEncodable. We will want a method on
ItemEncoder that takes an ItemObjectEncodable, and that should be
called `object` since it's a better approach than working ad-hoc with
tor_bytes::Writeable. (For example, an ItemObjectEncodable knows its
own label.)
So, rename `object` to `object_bytes`.
|
| |
|
|
| |
Typos found with codespell
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3571#note_3325449
|
| |
|
|
|
| |
This lets us having document items that are "manually non exhaustive"
which is necessary for struct literal constructors.
|
|
|
Signature encoding is not yet supported. We need to consider how this
will work.
|