On Wed, Jan 29, 2020 at 11:05 PM Axel Wagner
wrote:
> On Wed, Jan 29, 2020 at 12:57 PM Nigel Tao wrote:
>> For example, the https://golang.org/pkg/io/#LimitedReader struct just
>> exports its fields, and you use it like this
>> (https://go.googlesource.com/go/+/refs/heads/master/src/io/io_test.go
On Wed, Jan 29, 2020 at 12:57 PM Nigel Tao wrote:
> For example, the https://golang.org/pkg/io/#LimitedReader struct just
> exports its fields, and you use it like this
> (https://go.googlesource.com/go/+/refs/heads/master/src/io/io_test.go#39).
> There is no io.NewLimitedReader function.
>
Nit:
Great write-up.
> Keyword arguments should be added to the language.
In idiomatic Go, we often use struct literals (together with "make the
zero value useful", e.g. allocate map-typed fields lazily) instead of
object-creation functions:
x := &FooBar{
A: a,
B: b.c(),
}
instead of
x = newFo
Didn’t mean to imply anything negative - you accomplished what you set out to
do. I “think in Java” and a lot of my initial problems with Go revolved around
that, but even after doing some serious Go development - in the Go style - I
can agree with many of your points.
I will admit my bias agai
Most of the remainder of this post is asciidoc source, because that's easy
to quote. If you want to look at a nicely rendered version, see
https://gitlab.com/esr/reposurgeon/blob/master/GoNotes.adoc
= Notes on the Go translation of Reposurgeon =
version 1.8, 2020-01-25
This is an experience re
