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
{{ message }}
Repository navigation
proposal: testing: Support external packages to call testing.MainStart #51912
From the doc comments for Main, MainStart is preferred:
Systems simulating "go test" should be updated to use MainStart.
Previously, before go1.18, the internal interface testDeps could be satisfied by an external package. Upgrading to go1.18 the new internal interface contains methods with references to a private struct corpusEntry for the added fuzzing support. MainStart isn't part of the go compatibility promise. I propose providing an implementation of testDeps like
changed the title [-]testing: Support external packages to call testing.MainStart[/-][+]proposal: testing: Support external packages to call testing.MainStart[/+]on Mar 24, 2022
Activity
[-]testing: Support external packages to call testing.MainStart[/-][+]proposal: testing: Support external packages to call testing.MainStart[/+]seankhliao commentedon Mar 24, 2022
cc @bcmills
emcfarlane commentedon Mar 25, 2022
My mistake, struct isn't private but an alias:
go/src/internal/fuzz/fuzz.go
Line 459 in f985833
Would be nice to have a defined public testdeps implementation but not a blocker, happy to close.
ianlancetaylor commentedon Mar 30, 2022
Doesn't seem like there is anything we need to do here, so closing. Please comment if you disagree.