Closing the loop on this. They reached out in the Gopher Slack and we
pieced it together:
- https://gophers.slack.com/archives/C029RQSEE/p1592699134083700
It has to do with this section of code:
-
https://github.com/golang/go/blob/60f78765022a59725121d3b800268adffe78bde3/src/cmd/go/internal/ge
I think that this is a good question. I do question whether your code
examples are more or less simple when they are a single line. I'm worried
they may be more compact, which hurts the readability, while still
retaining the same complexity.
Being that you should be running `gofmt` before commi
Hey there,
I was working on updating a piece of software I maintain tonight to use Go
1.9, specifically I needed the monotonic time source in time.Time. I
decided I wanted to prevent my software from being compiled on anything
less than Go 1.9, because the behavior could be unexpected when a le
Hey there,
I saw your message / responded to it in the gophers Slack channel but I
thought I'd reply here too. I think one thing we should clarify for the
mailing list is that this _seems_ to impact Darwin (OS X) and not Linux,
based on testing done by users in Slack. I was also able to replica
at 12:17:27 PM UTC-7, Tim Heckman wrote:
>
> Hey Gophers!
>
> I'm working on a small project where I'm looking to support the
> "Forwarded" header as defined in RFC-7239[1]. For those unfamiliar, it's a
> standardization and unification of the "X-For
Hey Gophers!
I'm working on a small project where I'm looking to support the "Forwarded"
header as defined in RFC-7239[1]. For those unfamiliar, it's a
standardization and unification of the "X-Forwarded-For" and
"X-Forwarded-Proto" headers, among others. The simplest version of the
header loo
