Lessen config duplication in the code about i3status-rust

[pitkley]

Thanks for adding this issue, this is something I thought about while implementing the config-structs but didn't want to do in the same step. Very much 👍 on this!

[greshake]

In an ideal case, it would boil down to macro-usage like this, but I'm not sure how to realize it without (or even with) nightly features:

pub struct Temperature {
    text: ButtonWidget,
    output: String,
    [Configurable(false)] // Not required
    collapsed: bool,
    id: String,
    [Configurable(true)] // Required
    update_interval: Duration,
}
...
fn new(config: Config, _tx_update_request: Sender<Task>) -> Result<Self> {
    let default = Temperature {
        ... // Add default values here, dummy values for those that are required anyway
    };
    return util::configure(default, config)
}

[svmnotn]

@greshake uhmmm it might be possible but it would end up doing the same thing we are currently doing. AKA making a config struct and then using it to fill in the values.

[greshake]

The thing I was trying to get at may be a slightly different issue; I think there is a lot of unnessesary boilerplate which might get reduced and increase readability.

[svmnotn]

Maybe we should make a list of all the boiler plate and see what we can change using macros, and/or macros 1.1?
So far the config seems like the biggest boiler plate, but I didn't even notice it so I would like to know what you think could be improved @greshake.

[ammgws]

Closing due to inactivity