Peter Bourgon

@bcmills > I suspect that users will generally ignore the log message if it is not accompanied by instructions (or a tool!) to fix incompatible call sites, One, this proposal...

@myitcv @adg > > the golang-tools group has been discussing problems/solutions > > A little off topic in this thread, but: I would like to be involved but 15:30 UTC...

@rsc > As written, this proposal does not let a module author who is perfectly happy maintaining v1 and v2 indefinitely stop the (implicit) "you should update to v2" messages...

@bcmills > If a user has written an import statement, they got the idea to write that import from somewhere — a website (maybe pkg.go.dev or a code snippet from...

@rsc > I tend to agree with the point raised that for other commands, like go get itself, printing the message about v2 without a clear signal from the module...

Can you say a bit more why you want these changes? AppendSlice makes sense, but why the others?

Yeah, I'll probably add the MaxDepth option, and might add the AppendSlice option, but I think the KeyStringer bit is out of scope.

I think the nouns and verbs are too cute, and I think you're still exposing too much functionality to the end user. I want: ```go station, _ := patrol.NewStation(peer, peer,...

@yihuang > plugins are multi-process, file streamer should be ok with that, but in our versiondb case, we write to a db in a StreamingService while reading it to serve...

@yihuang > The implementation: [crypto-org-chain/cronos#722](https://github.com/crypto-org-chain/cronos/pull/722) It's an alternative db format to store historical versions of key-values, to reduce db size of certain types of archive nodes. It's written by a...