Records/golang/golang.org/x/tools/v0.45.0/golang.org/x/tools/go/ast/astutil.UsesImport

Published samples

• golang.org/x/tools v0.45.0: astutil.AddImport, astutil.Apply, astutil.DeleteImport Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWastutil.AddImportastutil.Applyastutil.DeleteImportastutil.UsesImporttxtar.Formattxtar.Parse MIT-0 · 2026-11-07

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-11-07

Failure clusters

• observed UNKNOWN exit 1 Evidence gap ×5 v0.0.0-20191112195655-aa38f8e97acc → v0.0.0-20200212150539-ea181f53ac56 → v0.1.5 → v0.45.0 os=linux · runtime=go@1.26 golang.org/x/tools/go/ast/astutil.UsesImport sha256:0882784d80c2…
  go: build output <str> already exists and is a directory
  go · unclassified-diagnostic · outer go build · gap stage-unknown
  Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-18 · Last seen: 2026-11-07
  Diagnostic re-verification candidate
  Where does this failure start and stop?