mirrors/arti.git/crates/tor-netdoc/src/parse/tokenize.rs, branch arti-v1.4.5

tor-netdoc: use more idiomatic rust

2025-04-03T17:36:25Z

tor-netdoc: fix `clippy::len_zero`

2025-04-03T17:32:58Z

```text warning: length comparison to one --> crates/tor-netdoc/src/parse/tokenize.rs:470:12 | 470 | if args.len() >= 1 { | ^^^^^^^^^^^^^^^ help: using `!is_empty` is clearer and more explicit: `!args.is_empty()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#len_zero note: the lint level is defined here --> crates/tor-netdoc/src/lib.rs:9:9 | 9 | #![warn(clippy::all)] | ^^^^^^^^^^^ = note: `#[warn(clippy::len_zero)]` implied by `#[warn(clippy::all)]` ```

netdoc: Reject BOMs and NULs.

2025-03-17T17:23:25Z

Per , our netdocs never have a BOM, and never have internal NULs. This makes Arti reject such documents. For arguments on why it's okay to increase parser strictness, see the (forthcoming) proposal 356 at torspec!342, and see older discussion at torspec#296. Closes #1739.

netdoc: Make some parsing init functions fallible.

2025-03-17T16:55:57Z

I'm about to make our parsers reject some strings at construction time, so it makes sense to have these functions become fallible. This is a breaking change.

Fix "clippy::manual-pattern-char-comparison" warning on nightly

2024-07-28T21:48:35Z

This warning suggests using `[a,b]` as a Pattern when it sees a search for `|ch| ch == a || ch == b`. (All of our supported rust versions allow this kind of Pattern.)

Run maint/add_warning.

2024-03-13T16:30:53Z

Run maint/add_warning to add lint block everywhere

2023-08-23T09:34:00Z

Run maint/add_warning to actually apply new lint allows

2023-07-10T12:49:51Z

netdoc: Rename parse_error_kind() to netdoc_error_kind().

2023-05-11T17:39:40Z

`ParseErrorKind` was renamed to `NetdocErrorKind`, so we need to rename this acccessor too. Signed-off-by: Gabriela Moldovan

netdoc: Rename `ParseError{Kind, Source}` to `NetdocError{Kind, Source}`.

2023-05-10T14:52:28Z

`ParseErrorSource` was originally meant to represent a parsing error, this enum has since gained some variants that aren't really parsing related (`Signature`, `CertSignature`, `UntimelyDescriptor`). Since this error type is now used for general-purpose netdoc errors, let's rename `ParseError{Kind, Source}` to `NetdocError{Kind, Source}`. Signed-off-by: Gabriela Moldovan