> It seems it's not so much booleans than using unnamed parameters for option parameters It's actually using unnamed parameters at all. While this issue is mor

> It seems it's not so much booleans than using unnamed parameters for option parameters It's actually using unnamed parameters at all. While this issue is more frequent for boolean parameters, it can happen for integers or floating point numbers as well. We do a lot of numerics in C, and calls such as optimize_foo (&state, 0.3f, 1e-5f, 1.f); have the same issues as mentioned in the post: Error prone, more difficult to review, more risky to refactor.