mirrors/arti.git/crates/tor-netdoc/src/lib.rs, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-11-24T16:06:22Ztor-netdoc: Move parse2/test.rs to test2.rs2025-11-24T16:06:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-24T15:57:42Zurn:sha1:8cdf8c36ddd0c966783d6300c76d909682928360
We're going to use this for the encoder testing too, so it needs to be
not buried inside parse2.
This commit is the file rename plus minimal changes to make it compile.
tor-netdoc: Make much more of the encode module contents public2025-11-18T20:58:16ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-12T15:00:00Zurn:sha1:56f193cc62c38f4cd126cfa1c2053a1fe4e02744
My planned new derive for encoding will be pub, but cfg gated, like
parse2 is.
tor-netdoc: Implement KeywordEncodable for &'static str2025-11-18T20:58:03ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-17T16:26:22Zurn:sha1:136b8b91cbd4b1d1bb56b7375efce8b1bbdce9d5
My planned encoding derive macro is going to provide keywords as
literal strings.
(The purpose of this trait is to allow the old parser to be generic
over its keyword constants, not to provide type-safety against passing
non-keyword strings to document encoders. Such bugs aren't very
likely and will be especially unlikely when we're deriving encoders.)
tor-netdoc: Split off Keyword::to_str into its own trait2025-11-18T20:58:03ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-17T16:22:03Zurn:sha1:ff88c5886866ae3cdb52f33773a41a8049a7b5cd
My planned encoding derive macro is not going to use `decl_keyword!`
but will need to call `NetdocEncoder::item`.
tor-netdoc: Introduce "encode" feature for the like-named module2025-11-10T19:30:48ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-07T18:04:50Zurn:sha1:31f1e62db6dea15bb325cb3d3477282ca8512829
We're going to introduce facilities for encoding more generally, and
we'll want a way to enable them.
Instead, have a separate feature for *encoding* documents.
tor-netdoc: Rename the `build` module to `encode`2025-11-10T18:51:50ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-07T18:03:01Zurn:sha1:fb8e7783e143a1950a9dc3f7a779732ae73023f9
The word "build" so often in Rust means builder pattern. This module
contains functions for encoding.
Fix name of clippy lint to unchecked_time_subtraction (2)2025-11-06T11:28:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-06T11:23:25Zurn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff
Run maint/add_warning
tor-netdoc: Reference `build::ItemArgument` from `NoramlItemArgument` doc2025-10-21T11:30:01ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-08T13:14:31Zurn:sha1:75948123302b3d83eb34a3f8d2fb7fab92ca7360
Since 9ce85acb3ab0d1a0b1be6ef0f10707983f4362a3
tor-netdoc: replace impl_item_argument_as_display with NormalItemArgument
this trait impl has implications for encoding as well as parsing.
tor-netdoc: Introduce `NormalItemArgument` impl-enabler trait2025-10-08T11:27:36ZIan Jacksonijackson@chiark.greenend.org.uk2025-10-06T14:50:09Zurn:sha1:c9a414ac29314bcbd285c55ccfb4cc54681d5fa7
This is currently used to enable `parse2::ItemArgumentParseable`.
In a moment it will enable `build::ItemArgument` too.
Remove "doc_auto_cfg" incantation from all crates.2025-09-29T19:30:03ZNick Mathewsonnickm@torproject.org2025-09-29T18:30:14Zurn:sha1:808b0ec2e3735a6dbbebeb857a3d6040ae02c697
This feature has been removed from nightly, in favor of doc_cfg.