mirrors/arti.git/crates/tor-proto/src/lib.rs, branch arti-v1.1.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.52023-01-27T13:27:47ZDisable clippy::unlinlined-format-args2023-01-27T13:27:47ZNick Mathewsonnickm@torproject.org2023-01-27T12:49:39Zurn:sha1:bf04641c6818cb2c87c6ed9cf463a5710f8919d2
This warning kind of snuck up on us! (See #748) For now, let's
disable it. (I've cleaned it up in a couple of examples, since
those are meant to be more idiomatic and user-facing.)
Closes #748.
Run add_warnings.2022-11-03T15:06:02ZNick Mathewsonnickm@torproject.org2022-11-03T15:06:02Zurn:sha1:932fe48eaf83f456eefd59475b4486d59966dec3cargo fmt to remove blank lines2022-10-12T14:29:04ZIan Jacksonijackson@chiark.greenend.org.uk2022-10-12T14:28:27Zurn:sha1:f84d8777db49f21ce6648dd244029531b370d5fd
Apparently cargo fmt doesn't like these, which my perl rune didn't
delete.
This commit is precisely the result of `cargo fmt`.
Replace all README copies in src/lib.rs with includes2022-10-12T14:29:03ZIan Jacksonijackson@chiark.greenend.org.uk2022-10-12T14:23:53Zurn:sha1:d9910dba0883020c7db08596f7b38e41875230f1
The feature we want is `#[doc = include_str!("README.md")]`, which is
stable since 1.54 and our MSRV is now 1.56.
This commit is precisely the result of the following Perl rune:
perl -i~ -0777 -pe 's{(^//!(?!.*\@\@).*\n)+}{#![doc = include_str!("../README.md")]\n}m' crates/*/src/lib.rs
enable doc_auto_cfg feature on every crate when documenting for docs.rs2022-08-24T16:22:41Ztrinity-1686atrinity@deuxfleurs.fr2022-08-17T19:13:13Zurn:sha1:7f939fa4804b3c934343141b79e8e2ded5fe0b0dRename ChannelsParams types to ChannelPaddingInstructions2022-08-17T09:54:41ZIan Jacksonijackson@chiark.greenend.org.uk2022-08-09T09:49:46Zurn:sha1:94dd3361e24335c187bbf4d3a3ec0971b186da3c
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2826167
This makes some lines too long; I will run rustfmt in a separate
commit for clarity.
tor-proto: Add a comment about the tor-proto layer.2022-08-10T16:13:01ZNick Mathewsonnickm@torproject.org2022-08-08T15:40:33Zurn:sha1:192a48c496b60a060aaa1dfdc9064b998f7bcdfb
We want to clarify that the tor-proto crate should only know _how_
its objects behave, not _why they behave that way_. (In other
words, we can have a "padding strategy" setting on a channel, but
not a "general usage" setting.)
Closes #531.
Clarify that tor-proto _does_ create timers.2022-08-10T16:02:46ZNick Mathewsonnickm@torproject.org2022-08-10T15:57:25Zurn:sha1:71242f1500db9216e101e5e8ec2292fc7918fd77tor-proto: Replace SecretBytes with SecretBuf.2022-08-01T19:41:22ZNick Mathewsonnickm@torproject.org2022-08-01T18:53:34Zurn:sha1:eedd63d5e9a4e055260b476177ee14972584a1bb
This does not yet make sure that `SecretBuf` is used where it
_should_ be, but at least it ensures that most uses of `SecretBytes`
will indeed act as intended, and make sure that whatever they
contain is zeroized.
It requires some corresponding changes to method calls for
correctness and type conformance.
Run maint/add_warning crates/*/src/{lib,main}.rs2022-06-23T18:15:42ZIan Jacksonijackson@chiark.greenend.org.uk2022-06-23T18:15:29Zurn:sha1:589c6e52bb49ccfe6c0ad9d18d6b994978e46c6c
Update all lint blocks