mirrors/arti.git/crates/tor-netdoc/src/parse, branch arti-v1.4.3

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 incorrect doc comment.

2024-10-09T16:06:01Z

Looks like a copy/paste error. Co-authored-by: Micah Elizabeth Scott

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

clippy: Replace many calls to .get(0) with .first()

2024-01-02T13:56:08Z

FTR I don't think agree with clippy on this question, but then I often don't.

netdoc: Remove an "unknown_lints" exception.

2023-11-30T15:16:10Z

Run maint/add_warning to add lint block everywhere

2023-08-23T09:34:00Z