Crates.io | fake_serialize |
lib.rs | fake_serialize |
version | 0.1.1 |
source | src |
created_at | 2020-01-09 15:26:50.861445 |
updated_at | 2020-01-09 15:29:28.243923 |
description | A rust macro for implementing dummy implementations of the traits serde::Serialize and serde::Deserialize |
homepage | |
repository | https://github.com/xemwebe/fake_serialize.git |
max_upload_size | |
id | 196924 |
size | 24,842 |
A rust macro for implementing dummy implementations of the traits serde::Serialize
and serde::Deserialize
Sometimes, you run in the problem to use some trait or function from an external crate, that is
constraint to types that implement the traits serde::Serialize
or/and serde::Deserialize
, even if
this is not an requirement for all use cases. Here, using a dummy implementation that just returns
an error if serialize
or deserialize
is calls comes handy.
This crate provides a derive macro that just provides these dummy implementations, e.g.
use fake_serialize::{FakeSerialize,FakeDeserialize};
#[derive(FakeSerialize,FakeDeserialize)]
struct SomeStruct {
...
}
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
License: MIT OR Apache-2.0