book

Learning Go, 2nd Edition

by Jon Bodner

January 2024

Beginner

494 pages

12h 30m

English

O'Reilly Media, Inc.

Book available

Read now

Unlock full access

Includes

Includes Quizzes

Has Sandbox

Who Should Read This BookConventions Used in This BookUsing Code ExamplesO’Reilly Online LearningHow to Contact UsAcknowledgments for the 2nd EditionAcknowledgments for the 1st Edition
Installing the Go ToolsTroubleshooting Your Go InstallationGo ToolingYour First Go ProgramMaking a Go Modulego buildgo fmtgo vetChoose Your ToolsVisual Studio CodeGoLandThe Go PlaygroundMakefilesThe Go Compatibility PromiseStaying Up-to-DateExercisesWrapping Up
The Predeclared TypesThe Zero ValueLiteralsBooleansNumeric TypesA Taste of Strings and RunesExplicit Type ConversionLiterals Are Untypedvar Versus :=Using constTyped and Untyped ConstantsUnused VariablesNaming Variables and ConstantsExercisesWrapping Up
Arrays—Too Rigid to Use DirectlySliceslenappendCapacitymakeEmptying a SliceDeclaring Your SliceSlicing SlicescopyConverting Arrays to SlicesConverting Slices to ArraysStrings and Runes and BytesMapsReading and Writing a MapThe comma ok IdiomDeleting from MapsEmptying a MapComparing MapsUsing Maps as SetsStructsAnonymous StructsComparing and Converting StructsExercisesWrapping Up
BlocksShadowing Variablesif for, Four WaysThe Complete for StatementThe Condition-Only for StatementThe Infinite for Statementbreak and continueThe for-range StatementLabeling Your for StatementsChoosing the Right for StatementswitchBlank SwitchesChoosing Between if and switchgoto—Yes, gotoExercisesWrapping Up
Declaring and Calling FunctionsSimulating Named and Optional ParametersVariadic Input Parameters and SlicesMultiple Return ValuesMultiple Return Values Are Multiple ValuesIgnoring Returned ValuesNamed Return ValuesBlank Returns—Never Use These!Functions Are ValuesFunction Type DeclarationsAnonymous FunctionsClosuresPassing Functions as ParametersReturning Functions from FunctionsdeferGo Is Call by ValueExercisesWrapping Up
A Quick Pointer PrimerDon’t Fear the PointersPointers Indicate Mutable ParametersPointers Are a Last ResortPointer Passing PerformanceThe Zero Value Versus No ValueThe Difference Between Maps and SlicesSlices as BuffersReducing the Garbage Collector’s WorkloadTuning the Garbage CollectorExercisesWrapping Up
Types in GoMethodsPointer Receivers and Value ReceiversCode Your Methods for nil InstancesMethods Are Functions TooFunctions Versus MethodsType Declarations Aren’t InheritanceTypes Are Executable Documentationiota Is for Enumerations—SometimesUse Embedding for CompositionEmbedding Is Not InheritanceA Quick Lesson on InterfacesInterfaces Are Type-Safe Duck TypingEmbedding and InterfacesAccept Interfaces, Return StructsInterfaces and nilInterfaces Are ComparableThe Empty Interface Says NothingType Assertions and Type SwitchesUse Type Assertions and Type Switches SparinglyFunction Types Are a Bridge to InterfacesImplicit Interfaces Make Dependency Injection EasierWireGo Isn’t Particularly Object-Oriented (and That’s Great)ExercisesWrapping Up
Generics Reduce Repetitive Code and Increase Type SafetyIntroducing Generics in GoGeneric Functions Abstract AlgorithmsGenerics and InterfacesUse Type Terms to Specify OperatorsType Inference and GenericsType Elements Limit ConstantsCombining Generic Functions with Generic Data StructuresMore on comparableThings That Are Left OutIdiomatic Go and GenericsAdding Generics to the Standard LibraryFuture Features UnlockedExercisesWrapping Up
How to Handle Errors: The BasicsUse Strings for Simple ErrorsSentinel ErrorsErrors Are ValuesWrapping ErrorsWrapping Multiple ErrorsIs and AsWrapping Errors with deferpanic and recoverGetting a Stack Trace from an ErrorExercisesWrapping Up

Repositories, Modules, and PackagesUsing go.modUse the go Directive to Manage Go Build VersionsThe require DirectiveBuilding PackagesImporting and ExportingCreating and Accessing a PackageNaming PackagesOverriding a Package’s NameDocumenting Your Code with Go Doc CommentsUsing the internal PackageAvoiding Circular DependenciesOrganizing Your ModuleGracefully Renaming and Reorganizing Your APIAvoiding the init Function if PossibleWorking with ModulesImporting Third-Party CodeWorking with VersionsMinimal Version SelectionUpdating to Compatible VersionsUpdating to Incompatible VersionsVendoringUsing pkg.go.devPublishing Your ModuleVersioning Your ModuleOverriding DependenciesRetracting a Version of Your ModuleUsing Workspaces to Modify Modules SimultaneouslyModule Proxy ServersSpecifying a Proxy ServerUsing Private RepositoriesAdditional DetailsExercisesWrapping Up
Using go run to Try Out Small ProgramsAdding Third-Party Tools with go installImproving Import Formatting with goimportsUsing Code-Quality Scannersstaticcheckrevivegolangci-lintUsing govulncheck to Scan for Vulnerable DependenciesEmbedding Content into Your ProgramEmbedding Hidden FilesUsing go generateWorking with go generate and MakefilesReading the Build Info Inside a Go BinaryBuilding Go Binaries for Other PlatformsUsing Build TagsTesting Versions of GoUsing go help to Learn More About Go ToolingExercisesWrapping Up
When to Use ConcurrencyGoroutinesChannelsReading, Writing, and BufferingUsing for-range and ChannelsClosing a ChannelUnderstanding How Channels BehaveselectConcurrency Practices and PatternsKeep Your APIs Concurrency-FreeGoroutines, for Loops, and Varying VariablesAlways Clean Up Your GoroutinesUse the Context to Terminate GoroutinesKnow When to Use Buffered and Unbuffered ChannelsImplement BackpressureTurn Off a case in a selectTime Out CodeUse WaitGroupsRun Code Exactly OncePut Your Concurrent Tools TogetherWhen to Use Mutexes Instead of ChannelsAtomics—You Probably Don’t Need TheseWhere to Learn More About ConcurrencyExercisesWrapping Up
io and FriendstimeMonotonic TimeTimers and Timeoutsencoding/jsonUsing Struct Tags to Add MetadataUnmarshaling and MarshalingJSON, Readers, and WritersEncoding and Decoding JSON StreamsCustom JSON Parsingnet/httpThe ClientThe ServerResponseControllerStructured LoggingExercisesWrapping Up
What Is the Context?ValuesCancellationContexts with DeadlinesContext Cancellation in Your Own CodeExercisesWrapping Up
Understanding the Basics of TestingReporting Test FailuresSetting Up and Tearing DownTesting with Environment VariablesStoring Sample Test DataCaching Test ResultsTesting Your Public APIUsing go-cmp to Compare Test ResultsRunning Table TestsRunning Tests ConcurrentlyChecking Your Code CoverageFuzzingUsing BenchmarksUsing Stubs in GoUsing httptestUsing Integration Tests and Build TagsFinding Concurrency Problems with the Data Race DetectorExercisesWrapping Up
Reflection Lets You Work with Types at RuntimeTypes, Kinds, and ValuesMake New ValuesUse Reflection to Check If an Interface’s Value Is nilUse Reflection to Write a Data MarshalerBuild Functions with Reflection to Automate Repetitive TasksYou Can Build Structs with Reflection, but Don’tReflection Can’t Make MethodsUse Reflection Only if It’s Worthwhileunsafe Is UnsafeUsing Sizeof and OffsetofUsing unsafe to Convert External Binary DataAccessing Unexported FieldsUsing unsafe ToolsCgo Is for Integration, Not PerformanceExercisesWrapping Up

Content preview from Learning Go, 2nd Edition

Preface

In the preface of the first edition, I wrote:

My first choice for a book title was Boring Go because, properly written, Go is boring….

Boring does not mean trivial. Using Go correctly requires an understanding of how its features are intended to fit together. While you can write Go code that looks like Java or Python, you’re going to be unhappy with the result and wonder what all the fuss is about. That’s where this book comes in. It walks through the features of Go, explaining how to best use them to write idiomatic code that can grow.

Go remains a small language with a small feature set. It still lacks inheritance, aspect-oriented programming, function overloading, operator overloading, pattern matching, named parameters, exceptions, and many additional features that complicate other languages. So why does a book on a boring language need an update?

There are a few reasons for this edition. First, just as boring doesn’t mean trivial, it also does not mean unchanging. Over the past three years, new features, tools, and libraries have arrived. Improvements like structured logging, fuzzing, workspaces, and vulnerability checking help Go developers create reliable, lasting, maintainable code. Now that Go developers have several years of experience with generics, the standard library has started to include type constraints and generic functions to reduce repetitive code. Even the unsafe package has been updated to make it a little safer. Go developers need a resource that ...