Pranav

I'm okay with `m_` prefix for member variables. I'm also okay with no special naming of private member functions since I agree with your points. I'm not particularly bothered by...

> Could you explain how it helps? It helps with a maintainability (see `nlohmann/json` example below) and flexibility w.r.t how the source is consumed (see `libfmt` example below). The change...

Sounds good to me. And yeah, I can add it to the Wiki once merged.

I agree with you on naming temporary variables/function args. * We can remove the `a` prefix on function arguments and `t` prefix on function-scope identifiers. - This was the naming...

I don't have one, no. For naming-related checks, e.g., `readability-identifier-naming.VariableCase`, it's probably worth our time to also address #133 where we can first change the coding style of the project.

I use a variation of that action in some private projects for work. [Here](https://github.com/p-ranav/StaticAnalysis)'s my fork of the action with some changes I wanted. And [here](https://github.com/p-ranav/StaticAnalysis-Test/pull/2) is an example project...

I like the plan and I agree with you - We can start small, from the current style and make incremental updates. I see what you have [here](https://github.com/skrobinson/argparse/pull/2) and It's...

Agreed on the definitions. 1. I'd like to keep support for compound arguments, e.g., `ps -aux` which is a combination of three short options: `-a`, `-u` and `-x`. 2. I'm...

Actions were designed to be similar to the visitor pattern in ANTLR - visit each argument/fragment, make changes given some context and save it. The parameter to .action() is a...

Understood. Just need some clarifications: What is the argument `s` in your example? Let's say the use-case is `--foo 1 2 3 4` Then is `s == 1`? What is...