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"});
}
  • o11c@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    The problem is that C++ compilers still haven’t fixed a trivial several-decades-old limitation: you still have to pass the named arguments in order.

    They use the excuse of “what’s the evaluation order”, but ordinary constructors have the exact same problem and they deal with that fine.

    • Renderwahn@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      It’s a bit annoying but why is it a problem? You still can skip arguments where you just want the default value. Compared to function arguments you also get defined evaluation order.