contact (at) mattcraig.me
Hmm. Checked the docs, looks like os.Create returns *File and err, but the sample doesn’t check that error.
Is it that the defer() that recovers is called before the defer() that closes (and potentially fails)?
I like the suggestion of having an explicit hard requirement that employees be willing to use and engage with the existing tech stack. It makes it easier to point to the requirements and say “you signed up for this”.…
As soon as I got the release email I came here to check if this had been posted to HN; it’s an incredible piece of work, and I highly recommend it. It sweeps away much of the mystery behind programming language…
Hmm. Checked the docs, looks like os.Create returns *File and err, but the sample doesn’t check that error.
Is it that the defer() that recovers is called before the defer() that closes (and potentially fails)?
I like the suggestion of having an explicit hard requirement that employees be willing to use and engage with the existing tech stack. It makes it easier to point to the requirements and say “you signed up for this”.…
As soon as I got the release email I came here to check if this had been posted to HN; it’s an incredible piece of work, and I highly recommend it. It sweeps away much of the mystery behind programming language…