Blog / Go Language Spec

Half way there

December 4, 2023

No live stream today. I’m still feeling a bit under the weather. Hopefully next week we’ll be back on schedule.

In January, I started this series on the Go spec, not having any idea if I'd have even 2 readers, or how long it would take to get through the whole spec.

This week we passed the half-way mark on that journey through the spec, and there are over 400 of you subscribed to this daily list. Thank you!

When I started the series, I had in the back of my mind that perhaps one day I would turn the series into a book. A sort of “Go Spec Study Bible”. I’m curious to know your thoughts, so I want to use this milestone to solicit your feedback. If you have a moment, would you hit reply, and let me know your thoughts?

  1. What have you learned during this series?
  2. How could the series be made more valuable to you?
  3. Would you find a this commentary on the Go spec valuable in book format?
  4. If so, would you be interested in receiving a free copy of the book, in exchange for providing your early feedback?

That’s it for now. Thanks for being part of this process!

Share this

Direct to your inbox, daily. I respect your privacy .

Unsure? Browse the archive .

Related Content

I'm looking for new clients

Could your project benefit from my expertise? I’ve had some availability open up in my schedule recently, so I’m announcing my new “Fractional Gopher” subscription service. I can help build your new features, pay down technical debt, audit your project’s code and architecture, or help in any number of ways. You’re already running my code in production. I’ve contributed to the Go standard library, as well as popular Go libraries such as echo, Logrus, and many others.

Bootstrapping

A quick note to say that I’m taking next week off, for a move. I expect to return October 4 with more Boldy Go: Daily emails. Until then! We’re down to the final two built-in functions in Go. And these are probably functions you should not be using, except possibly in throw-away test code or during debugging. Bootstrapping Current implementations provide several built-in functions useful during bootstrapping. These functions are documented for completeness but are not guaranteed to stay in the language.

Recover values

Handling panics … The return value of recover is nil when the goroutine is not panicking or recover was not called directly by a deferred function. Conversely, if a goroutine is panicking and recover was called directly by a deferred function, the return value of recover is guaranteed not to be nil. To ensure this, calling panic with a nil interface value (or an untyped nil) causes a run-time panic.

Get daily content like this in your inbox!

Subscribe