On Thu, Mar 25, 2021 at 7:34 AM Amnon <amno...@gmail.com> wrote: > I would check if it reproduces on Go 1.16.2 >
Testing whether a problem exists with the most release of a particular command (or project/ecosystem) is generally good advice. However, I don't see how your reply is useful, @Amnon Baron Cohen <amno...@gmail.com>, in this context. Had you pointed to a particular issue resolved between the 1.15.15 release, just four months ago, I would have agreed with your suggestion to attempt to reproduce the problem with the most recent Go release. -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- 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/CABx2%3DD-Udwm-_han-8s%3DgNZcTOk_om--9-JG2qtCnjZ6wFeTqQ%40mail.gmail.com.
