Recently I end up using structs everywhere as functions parameters to basically get named function parameters and better default arguments. Are there any downsides to this? So far the only annoying thing is to have to define those structs.
struct FunParams{
int i = 5;
float f = 3.14f;
std::string s = "hello";
};
void Fun(const FunParams& params){}
int main(){
Fun({.s = "hi there"});
}
Well, you can’t exactly have required parameters that way. At keast not to my knowledge
It is possible if they are added as regular function parameters before the struct parameter but somehow I find that a bit ugly…
I’m sure you can come up with some utility class
required(templated withT, Lemmy won’t let me) that isn’t default constructible but can be implicitly constructed from aT, then use this instead of typeTin the struct definition.