👋 Thanks for opening this issue!

Get help or engage by:

• /help : to print help messages.
• /assignme : to assign this issue to you.

There is an ongoing PR to make serde an optional feature:

• Improve: Make serde optional, a dirty work #243

What you need looks similar to this? An optional feature that enables several rkyv derive?

I do not have any experience on rkyv other than reading its API doc:)
A PR is welcomed! :DDD

Adding rkyv support would be a nice addition indeed. It's a very efficient format wrt (de)serialization speed which can easily become a bottleneck.

IMHO the solution outlined in the comment #243 (review) in the currently open serde PR would be a very simple and good solution wrt maintainablity.

Hi All, I'm looking at adding this feature and ran into a small issue. Is there any issue with moving away from using AnyError directly in some of the messages? An example:

(Edit)
I see now that the AnyError crate is actually apart of drmindrmer's repositories. I guess my question becomes if rkyv support should be added there?

(Edit 2)
Looking more closely at this, it doesn't appear that the error's themselves would/should ever be sent over the network so it doesn't look like there would be any reason to add this serialization to them. I should have a pr for this sometime today.

Hi All, I'm looking at adding this feature and ran into a small issue. Is there any issue with moving away from using AnyError directly in some of the messages? An example:

openraft/openraft/src/error.rs

Lines 314 to 320 in db047b9

	#[derive(Debug, Clone, PartialEq, Eq, thiserror::Error)]
	#[cfg_attr(feature = "serde", derive(serde::Deserialize, serde::Serialize), serde(bound = ""))]
	#[error("NetworkError: {source}")]
	pub struct NetworkError {
	#[from]
	source: AnyError,
	}

The issue being that AnyError is defined in the external crate so we can't easily add the rkyv traits to it

(Edit) I see now that the AnyError crate is actually apart of drmindrmer's repositories. I guess my question becomes if rkyv support should be added there?

(Edit 2) Looking more closely at this, it doesn't appear that the error's themselves would/should ever be sent over the network so it doesn't look like there would be any reason to add this serialization to them. I should have a pr for this sometime today.

It is possible to add rkyv to AnyError.

But AFAIK, only types that need to be persisted on disk need rkyv support.
Errors in openraft are only used for transport.
Does it have to be encoded in the rkyv format for transport?
E.g., for `send_append_entries():

The response and response errors are small structs, maybe it's possible to use some other serialization such as serde to encode responses?