In llvm-dwwarfdump --statistics output, "vars" refers to parameters and
local variables. Fix an issue where the scope bytes covered metric for
"vars" is unexpectedly low because parameter coverage isn't included.
This is one of those things where I am fine either way, we just should document what exactly the fields mean. (Could we even sneak the field description into the JSON output in a meaningful way?)
I will just add that we should try renaming the JSON fields (with a meaningful name) as well as the variables used to compute this numbers, since I am also always confused what the fields refers to :)
( at least, we can add a TODO marker there, and address that when we get a chance)
I think it would be reasonable to bump the version number and move to a coherent naming scheme. I came up with the original names in hurry while preparing for a dev meeting talk, I'm not wed to them :-)