The estargz/testutil.go and similar files leak the stdlib testing dependency into any production code that depends on these utilities. It would be ideal if the testing stuff was kept isolated from the core code to minimize transitive dependencies. This isn't a huge deal but still nice to have IMO.
I took a briefly look and the way things are structured makes it not trivial to do so
The
estargz/testutil.goand similar files leak the stdlibtestingdependency into any production code that depends on these utilities. It would be ideal if the testing stuff was kept isolated from the core code to minimize transitive dependencies. This isn't a huge deal but still nice to have IMO.I took a briefly look and the way things are structured makes it not trivial to do so