#[serde(skip_deserializing)] for Option<T> wrongly requires T to implement Default

[SylvainGarrigues]

Quoting the documentation for #[serde(skip_deserializing)]:
When deserializing, Serde will use Default::default() or the function given by default = "..." to get a default value for this field.

Option<T> defaults to None event if T doesn't implement Default, so why does the compiler complain T must implement such Default trait for me to be able to derive Deserialize?

Sample code (uncomment /* Default */ to have the code compile):

use serde::Deserialize;
use std::fmt::Debug;

#[derive(Debug /*, Default*/)]
struct Hidden(());

#[derive(Deserialize)]
struct Config<T> {
    ip: String,
    #[serde(skip_deserializing)]
    hidden: Option<T>,
}

fn load_config<T /*: Default*/>(s: &str) -> Config<T> {
    toml::from_str(s).unwrap()
}

fn main() {
    let config: Config<Hidden> = load_config(r#"ip = '127.0.0.1'"#);
    println!("ip={:?}, hidden={:?}", config.ip, config.hidden);
}

Same code in Rust playground

[SylvainGarrigues]

Oddly enough, I noticed that in my case, manually specifying the default function to Default::default() makes the code compile without restraining T to implement Default:

#[serde(skip_deserializing, default = "Default::default")]

[Mingun]

This is because serde_derive constraints generic types of the struct (T) to required traits instead of actual types of fields (Option<T>).

[avkonst]

And perhaps this ^ is a bug? I faced the same problem with serde(default) attribute for a field of custom generic type, which implements Default.

[avkonst]

Using the explicit path does not help either: