I’m one of the authors of this analyzer, and it’s surprising to see it here. To clear one misconception: some of the comments seem to be taking this as some ki

I’m one of the authors of this analyzer, and it’s surprising to see it here. To clear one misconception: some of the comments seem to be taking this as some kind of official Go tool, or using it a data point regarding the language itself. I don’t think this is justified; the analyzer is only used within the gVisor codebase, and is not an outgrowth of Go itself. On the points raised: I’m not a languages or compiler person; I think it’s pretty neat that I can write a decently powerful static analyzer using the same standardized packages used by vet and other tools. To me, this is the strength of Go: the core is simple. I agree with the idea that it would be cool if Go had some more advanced features in this area, but I also understand why these changes are made slowly, to ensure there’s experience and evidence. In the meantime, we’re free to write tooling that meets our specific needs (and lets one scratch a fun itch). One last thing: the README is incomplete and out of date (globals are supported, for example), but it was never really for public consumption.