remote-trait-object icon indicating copy to clipboard operation
remote-trait-object copied to clipboard

A simple and powerful Rust remote method invocation library based on trait objects

Results 13 remote-trait-object issues
Sort by recently updated
recently updated
newest added

It should always be imported. The policy to handle a not imported case is not decided

Since rust doesn't support async trait method, this will be a really exceptional interface.

Most of errors that caused by unexpected behavior of the other side's RTO port will just lead to panic. However, especially in Foundry context, the other port might have been...

And if the size is too small, it should be propagated as an error

It will check following assertions **eagerly**, so that it can fail quickly, not when there is an actual call later. - The given `HandleToExchange` is valid - The traits from...

- [ ] Export IDL from trait - [ ] Generate trait from IDL - [ ] Check compatibility between traits using IDL

Here's an instruction to profile the program. ``` cargo install flamegraph sudo apt-get install linux-tools-5.3.0-62-generic echo -1 | sudo tee /proc/sys/kernel/perf_event_paranoid echo 0 | sudo tee /proc/sys/kernel/kptr_restrict cargo flamegraph ```...

Two things must be supported for the local mock 1. `ServiceRef` now has third enum variant `Local`, which holds directly the smart pointer to service object 2. `ServiceRef::import()` to could...

You can utilize [trybuild](https://docs.rs/trybuild/1.0.30/trybuild/) crate for asserting the error message