mirrors/arti.git/crates/tor-netdoc/Cargo.toml, branch arti-v0.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.02022-04-01T13:15:18ZBump all arti*, tor* crates to 0.2.02022-04-01T13:15:18ZNick Mathewsonnickm@torproject.org2022-04-01T13:15:18Zurn:sha1:5b2fc118df0524144e6b2c34fdcce3d0fb692d24
Not all of these strictly need to be bumped to 0.2.0; many could go
to 0.1.1 instead. But since everything at the tor-rtcompat and
higher layers has had breaking API changes, it seems not so useful
to distinguish. (It seems unlikely that anybody at this stage is
depending on e.g. tor-protover but not arti-client.)
Typo fix.2022-03-31T14:34:11ZIan Jacksoniwj@torproject.org2022-03-31T14:34:11Zurn:sha1:68b614ade1a92e10cc81a3bb7b7a19a15fd48ddetor-netdoc: Conditionally expose document fields.2022-03-31T13:27:27ZNick Mathewsonnickm@torproject.org2022-03-31T13:20:21Zurn:sha1:b1b7ef00a0f96c3d878788cd890ed67656bcc1f4
This commit uses the `visibility` and `visible` crates to
conditionally make certain structs and their fields public
(respectively). This is incredibly dangerous to use for anything
besides testing, and I've tried to write the documentation for the
feature accordingly.
Merge branch 'slice-from-ref' into 'main'2022-03-14T13:14:05Zetator@eta.st2022-03-14T13:14:05Zurn:sha1:258e42ad3e7b1e2d0e315c0900794ebba8ce5dd1
Simpify tor-netdoc TokVal
See merge request tpo/core/arti!404tor-netdoc: reformat cargo.toml.2022-03-11T19:03:29ZNick Mathewsonnickm@torproject.org2022-03-10T21:00:04Zurn:sha1:3c9093f29409b3efbfa39fca9c73e7118dc4667b
This is the default vscode format, and seems popular elsewhere.
This commit does nothing but reformat.
tor-netdoc: Actually, make TokVal be a Vec2022-03-11T18:42:01ZIan Jacksonijackson@chiark.greenend.org.uk2022-03-11T18:42:01Zurn:sha1:888eea47b3ee03c28411c4abcc5eeca8b4088e40
This enum was otiose: its set of valid values is precisely those of a
Vec. (Indeed what would TokVal::Multi(vec![]) have meant?)
Add methods to `UnverifiedConsensus`2022-03-10T10:29:58ZChristian Grigischristian.grigis@epfl.ch2022-02-09T18:32:02Zurn:sha1:335af4ac30a1dcf4cc25ff5105f46a367c1ecbcbBump all crates to 0.1.02022-03-01T13:59:34ZNick Mathewsonnickm@torproject.org2022-03-01T13:59:34Zurn:sha1:e8e9791a9757a32779657c5284b380ae91ca7979Refactor tor_netdoc::Error2022-02-14T18:08:28ZNick Mathewsonnickm@torproject.org2022-02-14T18:08:28Zurn:sha1:b6d23c36bef1322e4fc6f89769222daa91c4d8f3
This error type doesn't impement HasKind, since the kind will depend
on context.
However, the existing implementation was pretty messy and inconsistent:
Some errors had positions, some didn't.
Some took messages as str, some as String.
Some had internal errors that were somewhat orthogonal to their actual
types.
This commit refactors tor_netdoc::Error to use a ParseErrorKind, and
adds a set of convenience functions to add positions and
messages to the errors that need them.
Bump the patch version of every crate that changed since 0.0.32022-01-31T15:30:52ZNick Mathewsonnickm@torproject.org2022-01-31T15:30:52Zurn:sha1:01d99373089f8131d1df9758fce45ffaa3fbf659