Closed azerupi closed 7 years ago
It's because I made rustc_serialize
the default feature for convenience and backward compatibility. In order to use serde_type
, you will need to disable it via --no-default-features
.
Is there a way to leave it as default feature but still disable it when serde_type
is enabled?
I think you could use something like below to only compile rustc-serialize
code when serde_type
isn't enabled
#[cfg(all(rustc-serialize, not(serde_type)))]
By the way, I am busy at the moment but I am willing to test this and make a PR later today if you agree :)
Nice! Thank you!
So when using the
serde_type
feature I get a compilation error. The compilation error actually originates in the handlebars crate but since I do not depend on it directly I was not sure where I should submit the issue.At first sight, it seems as enabling
serde_type
does not disablerustc-serialize
causing the double definitions.EDIT: It seems to compile fine with
default-features = false
but intuitively I would have assumed that just enablingserde_type
would take care of this. Would it be possible disablerustc-serialize
whenserde_type
is enabled?