tree 2a8ca5df611e6ef665bf63a07a8c0dc2d177de7d
parent 39bfef48d3b68fca9707aae7b9961202bc76ad55
author Alan Donovan <adonovan@google.com> 1689527682 -0400
committer Gopher Robot <gobot@golang.org> 1692980705 +0000

go/analysis/unitchecker: Example of separate analysis

This change adds an Example that demonstrates the
principle of separate analysis by having one program
(the manager) visit the import graph in postorder,
invoking a second program (the worker) as a child
process once per package.  The manager is analogous
to go vet, and the worker to the vettool.

Because unitchecker is closely coupled to go vet,
both in its config file, and in assumptions about
where and how facts and types are produced, this
change parameterizes unitchecker to illustrate
that not just facts but types too may be produced
by the worker, without the need for the compiler.
This may be a simpler and more efficient design
for (say) a distributed analysis system.

There are no changes to the public API yet
(a proposal will follow) so the example can't
yet serve directly as the basis for a new
implementation, but in the meantime it should
at least illuminate what is involved and,
perhaps, how unitchecker can be easily forked
and adapted.

The changes to unitchecker should not affect the
behavior of existing programs.

Change-Id: I4ae414ccde91853c77b8a45771dd6e5cfc015173
Reviewed-on: https://go-review.googlesource.com/c/tools/+/510215
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Robert Findley <rfindley@google.com>
Auto-Submit: Alan Donovan <adonovan@google.com>
Run-TryBot: Alan Donovan <adonovan@google.com>