tree eb63b185ac6f23c10d86e08055f4acadf2ffe93a
parent 442426e97dac359381288d5f22f804fcb6402a34
author Laura Peskin <pesk@google.com> 1613501181 +0000
committer CQ Bot <commit-bot@chromium.org> 1613501181 +0000

[config_parser] Fix off-by-one error in calculation of num_index_points

In https://fxrev.dev/485978, the config parser set the num_index_points
field of a ReportDefinition to the width of the range of valid integer
values when the integer range is small. However, we want to include both
endpoints of the integer range as index points, so the value of
num_index_points was off by 1 in that CL. This CL fixes that error +
some golint errors.

Change-Id: I3be8caa0d7b9f4c1f03adff049368ede377dc16a
Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/486957
Reviewed-by: Jared Weinstein <jaredweinstein@google.com>
Commit-Queue: Laura Peskin <pesk@google.com>