mirrors/arti.git/crates/tor-netdoc/src/doc/hsdesc/inner.rs, branch arti-v2.5.0

maint: Run maint/add_warning to deny string slices

2026-06-09T15:36:01Z

This commit executes maint/add_warning with the just added change to deny string slices except in tests. I recommend auditing this by checking out the previous commit followed by running the script yourself and then verifying that the diff is identical to this commit. This commit makes cargo clippy fail. We will add exceptions in the next commit.

tor-netdoc: Un-gate every cfg feature = "hsdesc-inner-docs"

2026-04-30T10:28:41Z

Part of #2492 phase 2.

netdoc: allow unstable_name_collisions lint for exactly_one()

2025-12-01T10:54:26Z

This silences a new warning on nightly.

Fix name of clippy lint to unchecked_time_subtraction (2)

2025-11-06T11:28:22Z

Run maint/add_warning

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again.

tor-netdoc: Removed dependency on `once_cell`

2025-06-15T02:11:18Z

- Replaced `once_cell::sync::Lazy` with `std::sync::LazyLock`. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

Resolve clippy warnings from 1.83

2025-05-13T18:53:41Z

Now that our MSRV is 1.83, clippy is happy to make more recommendations for us.

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.

PoW: Consolidate feature flags into a single flag.

2024-11-25T20:49:46Z

This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full features with a single hs-pow-full feature. It's possible that in the future we will want to split different schemes into different features, but we can do that when it comes up. For now, having this as a single flag makes it clearer what's going on, since the previous thing was not actually expressive enough to capture some things we care about (like "at least one pow scheme is enabled" that works in a future-compatible way). This change is not semver breaking since it's a experimental feature. Related: #1751

TimerangeBound: Stop using std::ops::Bound.

2024-11-25T18:20:11Z

Fixes: #1691