[temp.deduct.type] Remove excessive spacing in example #6541
Conversation
In core wording, there is a deliberate absence of a preferred style, so I wouldn't be so certain that this is "obvious". As far as I understand, Core does not want to insinuate that there is one preferred way to write C++. |
I understand that, but realistically speaking:
I doubt that putting a leading space only before the first parameter type in the function is intentional. To me this looks like an obvious stray space, since I yet have to meet a developer who writes code like this, and I doubt that clang-format can generate it. There may not be a single canonical style in the standard, but I still believe that the surrounding code in the same example can be used to infer what the author's intended style is. If that intended style isn't being followed, then it's simply a mistake. |
Firstly, the leading space in the parameter list of
g1,g2, andg3is obviously unintentional. This style isn't followed anywhere else in the example, and would be extremely unusual if intended.Secondly, the spacing in
fis quite excessive, and internally inconsistent with the remainder of the example. Just a few lines down, the example continues with:So everywhere but
f, the author has no problem using a very conservative amount of spacing for function pointers.This inconsistency tells me that the current declaration of
fis some in-dev version which only made it into the standard by accident.