4 ms·

Only "x/sys/unix" outside of tests/benchmarks ~/go/src/github.com/voidDB/voidDB git:(master) $ go run github.com/tailscale/depaware@latest g

by maxmcd 2y ago

Only "x/sys/unix" outside of tests/benchmarks ~/go/src/github.com/voidDB/voidDB git:(master) $ go run github.com/tailscale/depaware@latest github.com/voidDB/voidDB dependencies: (generated by github.com/tailscale/depaware) github.com/voidDB/voidDB/common from github.com/voidDB/voidDB+ github.com/voidDB/voidDB/cursor from github.com/voidDB/voidDB github.com/voidDB/voidDB/free from github.com/voidDB/voidDB github.com/voidDB/voidDB/node from github.com/voidDB/voidDB+ github.com/voidDB/voidDB/reader from github.com/voidDB/voidDB golang.org/x/sys/unix from github.com/voidDB/voidDB+ bytes from github.com/voidDB/voidDB+ cmp from internal/fmtsort+ encoding/binary from github.com/voidDB/voidDB/common+ errors from bytes+ D fmt from golang.org/x/sys/unix hash from github.com/voidDB/voidDB+ hash/fnv from github.com/voidDB/voidDB io from bytes+ io/fs from internal/filepathlite+ iter from reflect+ math from encoding/binary+ math/bits from golang.org/x/sys/unix+ os from fmt+ path from io/fs reflect from encoding/binary+ slices from encoding/binary+ LD sort from golang.org/x/sys/unix strconv from fmt+ LD strings from golang.org/x/sys/unix sync from encoding/binary+ sync/atomic from internal/bisect+ syscall from github.com/voidDB/voidDB/cursor+ time from github.com/voidDB/voidDB+ unicode from bytes+ W unicode/utf16 from internal/poll+ unicode/utf8 from bytes+

joel-ling 2y ago
Thank you for showing substantive evidence in defence of voidDB; it is very vindicating.
- ncruces 2y ago
  It doesn't take much to split your go.mod file require blocks into needed dependencies, and test dependencies, with a few comments explaining the why of each dependency. Go tooling will preserve your go.mod comments and structure. You can also consider moving integration tests and benchmarks to another module in the same repo.
  - joel-ling 2y ago
    Great ideas. I have broken out the tests into their own modules within the same repository. Thanks!

by maxmcd 2y ago

joel-ling 2y ago

Thank you for showing substantive evidence in defence of voidDB; it is very vindicating.

ncruces 2y ago
It doesn't take much to split your go.mod file require blocks into needed dependencies, and test dependencies, with a few comments explaining the why of each dependency. Go tooling will preserve your go.mod comments and structure. You can also consider moving integration tests and benchmarks to another module in the same repo.
- joel-ling 2y ago
  Great ideas. I have broken out the tests into their own modules within the same repository. Thanks!