mirrors/arti.git/crates/tor-cell/src/restrict.rs, branch arti-v1.3.1

Fix indentation from last commit.

2024-05-07T16:23:39Z

tor-cell: Allow unuexpected_cfgs in restricted macro.

2024-05-07T16:22:16Z

(We need this to permit our usage of our $omit_from hack.)

tor-cell: Stop using deprecated name in doctest

2023-12-14T20:11:39Z

tor-cell: Implement {Relay,Chan}Msg for every body type

2023-02-15T15:48:19Z

This will make it ergonomic to decode a single body type without having to declare a variant that accepts only a single message.

tor-cell: Return a useful error when restrist_msg rejects a command.

2023-02-09T15:20:31Z

Change tor_bytes::Error::BadMessage to a Cow.

2023-02-09T15:20:31Z

Actually, to avoid making a breaking change, I'm deprecating BadMessage and creating a new InvalidMessage variant that takes a Cow. This way I don't need to track every crate that re-exposes tor_bytes::Error and call this a breaking change in those. Making this change will allow tor_bytes errors to be much more helpful.

tor-cell: Re-export paste so restrict_msg can work outside the crate.

2023-02-09T15:20:31Z

tor-cell: Make RelayEarly a separate type.

2023-02-09T15:20:28Z

This allows us to remove a shenanigan from `restricted_msg!{}`.

tor-cell: Have restrict_msg add conversion functions.

2023-02-09T15:20:11Z

Every FooMsg type now implements Into, and TryFrom. Additionally, it now implements From for every distinct type that it supports. This last part lets us discard a bunch of code. Unfortunately, I needed some downright hackish trickery in order to get these macros to avoid generating `From for AnyFooMsg` and conflicting with the blanket implementation. The trickery to deal with RelayEarly and Relay being the same type was not necessarily worth it; I will be separating them and removing said trickery in the next commit.

tor-cell: documentation cleanups related to restricted_msg

2023-02-07T21:03:14Z