Are these existing known bugs or did you open a ticket on the Go bug tracker? If there are already tickets for these known bugs, you should mention the ticket number in your code review. If there aren't tickets, you should probably start by opening a ticket and then linking to your changes.
As for your feature/improvement, it's also generally best to discuss such things as an issue or on the go-dev mailing list before digging in, if only so you don't waste time working on things that may not be accepted. Here's a link to Go's contribution guide if you haven't seen it: https://go.dev/doc/contribute On Monday, October 10, 2022 at 11:32:15 AM UTC-4 zept...@gmail.com wrote: > Hi Gophers! > > Does anyone know if the jsonrpc2 sub-directory of golang.org/x/exp is > still maintained? > > If yes, perhaps could you point me to the right person? as there are 2 > pending bug fixes that do not seem to arouse somebody curiosity :) > > https://go-review.googlesource.com/c/exp/+/412334 > https://go-review.googlesource.com/c/exp/+/436888 > > As I am here, I also proposed a slight improvement to expose errors > content to the caller: > > https://go-review.googlesource.com/c/exp/+/415615 > > Thanks for your help. > > Regards, > > Max. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/40d9fd5e-ffce-45d6-b063-f030ddae0a09n%40googlegroups.com.
