On Monday, April 25, 2022 at 8:12:35 AM UTC+2 kortschak wrote:
> On Mon, 2022-04-25 at 05:39 +, 'Dan Kortschak' via golang-nuts
> wrote:
> >
> > I suspect that this is from GitHub checking out the code on windows
> > with autocrlf and so converting perfectly sensible \n to \r\n, which
>
On Monday, April 25, 2022 at 2:12:35 AM UTC-4 kortschak wrote:
> I have sent https://go-review.googlesource.com/c/go/+/402074 to address
> this.
>
>
Dan,
For the second and subsequent lines,
for _, line := range lines[1:] {
line = bytes.TrimSpace(line)
// ...
}
Did you consider be
On Mon, 2022-04-25 at 05:39 +, 'Dan Kortschak' via golang-nuts
wrote:
>
> I suspect that this is from GitHub checking out the code on windows
> with autocrlf and so converting perfectly sensible \n to \r\n, which
> is
> then not properly handled by this
>
https://github.com/golang/go/blob/96c8c
On Sun, 2022-04-24 at 05:21 -0700, Tiago Katcipis wrote:
> Hi,
>
> I was playing around with Go's fuzz support on a pet project of mine
> and as the fuzzer found some offending inputs it created the corpus
> entries on the file system. I fixed the issues but then something
> interesting happened on
