Are Serialize and Deserialize required for in-memory transports?

[anna-hope]

Thanks so much for this crate!

I have this kind of service definition:

#[derive(Debug)]
struct Boo;

#[tarpc::service]
trait BooService {
    async fn boo() -> Boo;
}

I am getting

error[E0277]: the trait bound `service::Boo: serde::Serialize` is not satisfied

I was planning to use this service with an in-memory transport from tarpc::transport::channel, and so I wouldn't need to serialise/deserialise the data. I also didn't enable any optional features in tarpc, which I believe include serde (at least, I didn't enable them for this specific crate; I have another crate in the workspace that is using serde_transport). I do have serde as a dependency this crate in general, though.

Do my types still need to have Serialize and Deserialize, even with an in-memory transport? It's ultimately not a big deal, as I can add them, but I wanted to make sure, in case there's something I missed.

Update: I checked in a new project, and the same code worked fine. Hm. I wonder if serde being part of the crate is causing this somehow.

Update 2: The error about unsatisfied serde::Serialize only fires when I build the workspace, not the individual crate. I guess it's something in my workspace setup. Closing for now, unless I find something relevant.

[tikue]

Serialization is definitely meant to be optional; feel free to reopen if you continue to face issues!