In D19201#768693, @baloghadamsoftware wrote:

There is a patch (D33537) for a check which is a superset of this: [...] A more important difference is that we traverse the whole call-chain and check all the throw statements and try-catch blocks so indirectly throwing functions are also reported and no flase positives are caused by throw and catch in the same try block.

Cosmetic

Removed unnecessary colon from message

Docs and cosmetic issues

Fixed false positive issues

Improved messages, added tests with templates, fixed some typos.

I took advantage of new getExceptionSpecSourceRange (it wasn't available before) instead of getting exception specification manually with the lexer.

LGTM

What's happening here? It's accepted, but not merged and the last activity is 3 months old while my change is waiting for it. Can I help somehow?

Thanks for review, guys. I fixed as many easy problems as I had time for today, will continue later.

Note `FunctionProtoType::getNoExceptExpr` is weird. If you have the same expr in multiple noexcepts, then it returns the same object for all of them, so it is useless for determining the location in code.