Damien Neil

Code is read much more often than it is written. I don't believe saving a little typing is worth a change to the language syntax here. The advantage, if there...

> Whatever the approach, if there's any change, I believe it will need to be regular and apply to any function. I don't quite follow this. Function declarations necessarily must...

@griesemer Thanks; I (mostly) agree with that point. I think the interesting question for this proposal is whether having some syntax is a good idea or not; what that syntax...

The feature request is to respond to an HTTP request on an HTTPS port with a configurable error message. Testing several major websites (www.google.com, www.amazon.com, www.microsoft.com), none of them respond...

> They all jump to https with the same port: An `https://` URL with no port uses a default port of 443, not 80. All these are redirecting from HTTP...

It looks like nginx responds to an HTTP request on an HTTPS port with an error 497 (an nginx-specific code), and permits code-specific error handler overrides. The example nginx configuration...

I'm reopening this issue to bring up the question of what CopyFS should do if the destination contains a symlink. If I `CopyFS("dir", fsys)`, fsys contains a file etc/evil, and...

Updated documentation to state that symlinks in the destination are followed.

Thanks for the nice analysis (and the fix!). @gopherbot please open backport issue for go1.21. This is significant regression with no workaround.

It probably does make sense for `quic.Stream` to implement `net.Conn`. I don't think it's useful for anything in a QUIC implementation to implement `net.Listener`. A `quic.Listener` isn't a `net.Listener`, because...