mirrors/arti.git/crates/tor-rpcbase/src/method.rs, branch arti-v1.2.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.52024-06-17T18:13:06ZChange deftly syntax to post 0.12.1 version2024-06-17T18:13:06ZIan Jacksonijackson@chiark.greenend.org.uk2024-06-17T17:33:09Zurn:sha1:dddf07561868579ea687eeadaa8f863aa833c764
* Change `pub` to `export`
* Change the `=` in define to `:`
* Change `pub_template_semver_check` to `template_export_semver_check`
Right now, 0.12.1 supports both syntaxes. I have verified this branch
also compiles with
https://gitlab.torproject.org/Diziet/rust-derive-deftly/-/merge_requests/402
ee171ffaf56d7dcb7d75584054921153fe19b222
Add a few "TODO RPC" notes2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-16T12:35:18Zurn:sha1:854b1507c95ca7edde01c545b0c7375912168944RPC: Fill in documentation about invoke_special2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T18:45:48Zurn:sha1:69510aaa1750362d6df9d7e92b9b139d70071e17RPC: Require an Error type in methods.2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T18:19:30Zurn:sha1:98765e5a4cdf70356db38d324b0896d2b6f83c2f
This is needed so that we can cast special methods' return types
properly.
I wish I could make this optional, but Rust doesn't allow
defaulting an associated type.
Relax Serialize requirement on method outputs.2024-05-16T12:40:06ZNick Mathewsonnickm@torproject.org2024-05-14T17:36:17Zurn:sha1:704b1ec7f9e92208b548ebf0e9ee50adfe9aa0d0
Now Methods can return anything; and only if their outputs are
Serialize will they implement RpcInvocable.
rpc: Move typetag onto subtrait of DynMethod2024-05-16T12:40:04ZNick Mathewsonnickm@torproject.org2024-05-14T15:21:02Zurn:sha1:0e8608ba76f61a401040c8f762b99e5f3965d8e8
This will allow us to create dispatchable methods that are only
invoked from inside the arti code, and are not themselves
serializable.
RPC: Enforce method name format.2024-05-14T13:39:47ZNick Mathewsonnickm@torproject.org2024-05-14T13:35:19Zurn:sha1:8da4b96991c01ff16bd1194bca77d9bedf0bb9fa
We need to do this carefully, since we want our system to be
extensible with new namespaces.
First, when we are constructing an RpcMgr, we _warn_ about any
method names that are misformed.
Second, we add a test in the `arti` crate to fail if any method
names are invalid. This will only catch method names in crates that
`arti` depends on.
rpc: Remove a limitation on DynMethod macro.2024-05-06T13:12:08ZNick Mathewsonnickm@torproject.org2024-04-24T15:08:16Zurn:sha1:4f414cbbdac72433a21642beb352dc69348b8525
It no longer requires the user to have `typetag` in scope.
rpc: Revise backend for dispatchable-object macro.2024-04-22T16:02:29ZNick Mathewsonnickm@torproject.org2024-04-11T14:44:17Zurn:sha1:640af8c9c7f79ca033d766391b12c2f30a7f26fd
The trick here is to provide an `Invoker` trait,
with blanket implementations for appropriate `fn(_,_,_,_?) -> _`.
With this trick, we no longer need to have a `decl_rpc_invoke_fn`.
This lets us discard HasConstTypeId entirely,
and will let us simplify some other syntax moving forward.
rpc: Move deftly attributes into an `rpc` namespace.2024-04-11T12:56:53ZNick Mathewsonnickm@torproject.org2024-04-11T12:56:53Zurn:sha1:f96ca62bed8bd1ab42fc069331aef049e9c4515e