summaryrefslogtreecommitdiff
path: root/clippy.toml
Commit message (Collapse)AuthorAgeFilesLines
* clippy: Add an xref re random_range to the commentIan Jackson2026-05-131-0/+1
| | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3982#note_3410614
* clippy: disallow random_range standalone method tooIan Jackson2026-05-131-0/+1
| | | | | Upstream rand have provided a convenient alias for causing your program to panic. How helpful.
* clippy: Work around bug where it claims method doesn't existIan Jackson2026-05-131-1/+6
| | | | | | | | | | | | Fixes warning: `rand::RngExt::random_range` does not refer to a reachable function --> /volatile/rustcargo/Rustup/Arti/arti/clippy.toml:7:5 | 7 | { path = "rand::RngExt::random_range", reason = "Prefer tor_basic_utils::RngExt::gen_range_checked to avoid uncontrolled panics, or gen_range_infallible if applicable" }, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: add `allow-invalid = true` to the entry to suppress this warning
* Upgrade rand crates to 0.10.Wesley Aptekar-Cassels2026-05-121-2/+1
| | | | | | | | | | | When the circ-padding feature is enabled, we use maybenot, which does not yet support rand 0.10. In the meantime, enabling this feature pulls in rand 0.9. This is not ideal, but should be okay as a temporary situation. This also replaces the use of ReseedingRng (which was removed in 0.10) with the reseeding_rng crate. This is somewhat less performant, but it should be okay.
* clippy.toml: Forbid the various "now" methods.Nick Mathewson2026-03-261-0/+3
| | | | | By doing this, we make sure that everybody is using the correct types and methods.
* maint: warn if `retain` method is used from 'weak_table' crateSteven Engler2026-01-121-0/+8
| | | | | | | | | | The retain method is broken on these types. I only tested `WeakValueHashMap` and `WeakHashSet`, but it's likely that the other types are broken as well. We don't use this method currently, but it would be easy to accidentally use it in the future. Let's try to catch this bug early, and if it happens to get fixed, then it's easy to remove this lint.
* refactor: convert Extend to inherent method, forbid push/extend, fix ↵Nihal2025-12-171-0/+1
| | | | rend_handshake time
* refactor: remove early returns and forbid push() via clippyNihal2025-12-171-0/+1
|
* maint: add clippy warning for `futures::task::SpawnExt`Steven Engler2025-11-041-0/+1
|
* squash! Upgrade rand dependency to 0.9.Nick Mathewson2025-03-181-0/+1
| | | | - `Rng::gen_range()` has been renamed to `Rng::random_range()`
* clippy: Disallow Path::exists().Gabriela Moldovan2024-07-301-0/+1
| | | | Part of #1493
* Forbid Path::displayIan Jackson2024-03-051-0/+1
|
* oneshot: Deprecate futures::channel::oneshotIan Jackson2023-10-111-0/+5
|
* rng ranges: Forbid use of panicky Rng::gen_rangeIan Jackson2023-07-101-0/+1
| | | | Fixes #920
* Fix typoDimitris Apostolou2022-03-301-1/+1
|
* Remove allow(clippy::disallowed_methods) lint.Nick Mathewson2022-03-301-1/+1
|
* remove most usage of SystemTime::nowtrinity-1686a2022-02-251-0/+3