I'm considering adding some stricter checks to tast-lint to make code reviews easier, but there will be a higher risk of false positives. It probably makes sense to support NOLINT comments so that issues can be suppressed.

It looks like tast-lint already supports NOLINT for ignoring golint warnings, but supporting it for our custom checks (which use ast.Walk) seems a bit trickier. I think I found an approach that works, though.