| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
We must generally set such a field to the default.
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3985#note_3413183
|
| |
|
|
|
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3985#note_3413182
I left the word "fixed" in some of the docs and error messages, where
it seemed to make sense.
|
| |
|
|
| |
We're going to want quite a lot of this for eg network-status-version.
|
| | |
|
| |\
| |
| |
| |
| | |
Add debugging support to ItemValueParseable derive
See merge request tpo/core/arti!3881
|
| | |
| |
| |
| |
| |
| | |
Without this adding `#[deftly(netdoc(debug))]` can fail to build,
because the encoding module doesn't have `io::Write` in its `pub use`.
(Unlike parse2, it doesn't have a separate macro prelude.)
|
| | |
| |
| |
| | |
Ie for "arguments" that don't actually appear.
|
| |/
|
|
| |
T_SIGNATURES is false, just above.
|
| |\
| |
| |
| |
| | |
tor-netdoc: Three fixes to parsing and encoding
See merge request tpo/core/arti!3862
|
| | |
| |
| |
| |
| | |
The type error's span now points at the field type, rather than into
the macro.
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
| |
Now some bugs have become visible.
* Properly ``-quote the name in the heading.
* Add a missing space before `{`
* Adjust the fields to level-4 indent.
* In `construct()`, ``-quote the name, and xref it in the body,
not the title (which rustdoc makes a link to the fn itself)
|
| |
|
|
|
|
| |
This lines all the docs lines up, so we can see our indentation.
No change to the generated docs.
|
| |
|
|
| |
No change to the generated docs.
|
| |
|
|
|
|
| |
The hidden __non_exhaustive field has to be pub.
And, fix the use site, currently AuthCert.
|
| |
|
|
| |
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.
|
| |
|
|
|
|
| |
This is going to be its own trait and it is usually best if macros are
named after traits, rather than having the macro derive a different
trait depending on meta attributes.
|
| |
|
|
| |
With `#[non_exhaustive]`, you're not allowed to write even `Thing { ..base }`.
|
| |
|
|
|
| |
This lets us having document items that are "manually non exhaustive"
which is necessary for struct literal constructors.
|
| | |
|
| |
|
|
| |
Let's not ask users to refer to the Constructor derive macro docs.
|
| | |
|
| |
|
|
| |
This doesn't actually work of course.
|
| |
|
|
|
|
|
|
| |
We want to recognise `#[deftly(netdoc(debug))]` because otherwise we
have to make lots of these attributes conditional.
So, implement it for *all* the derives, providing a nugatory debug
statement.
|
| |
|
|
| |
This makes it possible to use $F_KEYWORD_REPORT within another concat.
|
| |
|
|
|
|
| |
Code motion fromk NetdocParseableFields to NetdocFieldsDeriveCommon.
This uses the derive-deftly imported doc comment feature.
|
| |
|
|
| |
Code motion from NetdocParseable to NetdocEntireDeriveCommon.
|
| |
|
|
| |
Code motion from ItemValueParseable to NetdocItemDeriveCommon.
|
| |
|
|
|
|
|
|
| |
Code motion from NetdocParseable to NetdocEntireDeriveCommon.
Code motion from NetdocParseableFields to NetdocFieldsDeriveCommon.
Again, the encoder wants exactly this logic.
|
| |
|
|
|
|
|
| |
Code motion from NetdocSomeItemsParseableCommon to
NetdocSomeItemsDeriveCommon.
Encoding wants exactly the same logic.
|
| |
|
|
|
|
|
| |
There is nothing actually in any of these yet. But it is most
convenient to lay out the structure now.
We'll move code into these modules in forthcoming commits.
|
| |
|