You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some vet checks could be short-circuited at the file level. For example, the unsafe
pointer checker could avoid running if unsafe has not been imported. Something similar
holds for the atomic check, the cyclic finalizer test, and the template check (if it
goes in). The asm check could probably be run only on .s files.
The text was updated successfully, but these errors were encountered:
I ran a quick test that short-circuits the atomic and unsafe checks at the file level.
Those are the only clear file-level wins available at tip. It cut 3.5% off wall clock
time, so not high priority.
The implementation needs more thought; vet's structure is complicated already.
For future reference, the quick test referred to above is at https://codereview.appspot.com/106510044/. (I don't plan to migrate it to Gerrit but want others to be able to find it in the future if they want.)
mikioh
changed the title
go.tools/cmd/vet: add hook for file level checker short-circuits
cmd/vet: add hook for file level checker short-circuits
Jan 10, 2015
mvdan
changed the title
x/tools/cmd/vet: add hook for file level checker short-circuits
cmd/vet: add hook for file level checker short-circuits
May 31, 2018
The text was updated successfully, but these errors were encountered: