はてなブックマーク

The general form of the language tag is a language code (“en”, “cmn”, “zh”, “nl”, “az” above) followed by an optional subtag for script (“-Arab”), region (“-US”, “-BE”, “-419”), variants (“-oxendict” for Oxford English Dictionary spelling), and extensions (“-u-co-phonebk” for phone-book sorting). The most common form is assumed if a subtag is omitted, for instance “az-Latn-AZ” for “az”. The most c

Tips for writing clear, performant, and idiomatic Go code

Andrew Gerrand 19 August 2015 Today the Go project is proud to release Go 1.5, the sixth major stable release of Go. This release includes significant changes to the implementation. The compiler tool chain was translated from C to Go, removing the last vestiges of C code from the Go code base. The garbage collector was completely redesigned, yielding a dramatic reduction in garbage collection paus

Russ Cox 8 July 2015 Welcome [This is the text of my opening keynote at Gophercon 2015. The video is available here.] Thank you all for traveling to Denver to be here, and thank you to everyone watching on video. If this is your first Gophercon, welcome. If you were here last year, welcome back. Thank you to the organizers for all the work it takes to make a conference like this happen. I am thril

Yang Zhou 6 July 2015 This guest blog post was written by Yang Zhou, Software Engineer at Qihoo 360. Qihoo 360 is a major provider of Internet and mobile security products and services in China, and operates a major Android-based mobile distribution platform. At the end of June 2014, Qihoo had about 500 million monthly active PC Internet users and over 640 million mobile users. Qihoo also operates

Andrew Gerrand 7 May 2015 Introduction Godoc examples are snippets of Go code that are displayed as package documentation and that are verified by running them as tests. They can also be run by a user visiting the godoc web page for the package and clicking the associated “Run” button. Having executable documentation for a package guarantees that the information will not go out of date as the API

Sameer Ajmani 4 February 2015 Introduction Go code is organized into packages. Within a package, code can refer to any identifier (name) defined within, while clients of the package may only reference the package’s exported types, functions, constants, and variables. Such references always include the package name as a prefix: foo.Bar refers to the exported name Bar in the imported package named f

Rob Pike 12 January 2015 A common point of discussion among Go programmers, especially those new to the language, is how to handle errors. The conversation often turns into a lament at the number of times the sequence if err != nil { return err } shows up. We recently scanned all the open source projects we could find and discovered that this snippet occurs only once per page or two, less often th

Rob Pike 22 December 2014 A property of universal computation—Turing completeness—is that a computer program can write a computer program. This is a powerful idea that is not appreciated as often as it might be, even though it happens frequently. It’s a big part of the definition of a compiler, for instance. It’s also how the go test command works: it scans the packages to be tested, writes out a

Andrew Gerrand 10 December 2014 Today we announce Go 1.4, the fifth major stable release of Go, arriving six months after our previous major release Go 1.3. It contains a small language change, support for more operating systems and processor architectures, and improvements to the tool chain and libraries. As always, Go 1.4 keeps the promise of compatibility, and almost everything will continue to

Tips for writing clear, performant, and idiomatic Go code

Andrew Gerrand 26 September 2014 Introduction This week Docker announced official base images for Go and other major languages, giving programmers a trusted and easy way to build containers for their Go programs. In this article we’ll walk through a recipe for creating a Docker container for a simple Go web application and deploying that container to Google Compute Engine. If you’re not familiar w

Rob Pike 25 August 2014 Introduction Go is a statically typed language that does not permit operations that mix numeric types. You can’t add a float64 to an int, or even an int32 to an int. Yet it is legal to write 1e6*time.Second or math.Exp(1) or even 1<<(' '+2.0). In Go, constants, unlike variables, behave pretty much like regular numbers. This post explains why that is and what it means. Backg

Tips for writing clear, performant, and idiomatic Go code

Tips for writing clear, performant, and idiomatic Go code

Tips for writing clear, performant, and idiomatic Go code

Andrew Gerrand 18 June 2014 Today we are happy to announce the release of Go 1.3. This release comes six months after our last major release and provides better performance, improved tools, support for running Go in new environments, and more. All Go users should upgrade to Go 1.3. You can grab the release from our downloads page and find the full list of improvements and fixes in the release note

Tips for writing clear, performant, and idiomatic Go code

Andrew Gerrand 23 September 2010 Concurrent programming has its own idioms. A good example is timeouts. Although Go’s channels do not support them directly, they are easy to implement. Say we want to receive from the channel ch, but want to wait at most one second for the value to arrive. We would start by creating a signalling channel and launching a goroutine that sleeps before sending on the ch

Tips for writing clear, performant, and idiomatic Go code

Go Turns 15, 11 November 2024 Austin Clements, for the Go team Happy 15th birthday, Go! What's in an (Alias) Name?, 17 September 2024 Robert Griesemer A description of generic alias types, a planned feature for Go 1.24 Building LLM-powered applications in Go, 12 September 2024 Eli Bendersky LLM-powered applications in Go using Gemini, langchaingo and Genkit Share your feedback about developing wit

Tips for writing clear, performant, and idiomatic Go code

Tips for writing clear, performant, and idiomatic Go code

Andrew Gerrand and Johan Euphrosine 13 December 2013 Background When we launched Go for App Engine in May 2011 the SDK was just a modified version of the Python SDK. At the time, there was no canonical way to build or organize Go programs, so it made sense to take the Python approach. Since then Go 1.0 was released, including the go tool and a convention for organizing Go programs. In January 2013

The playground service has three parts: A back end that runs on Google’s servers. It receives RPC requests, compiles the user program using the gc tool chain, executes the user program, and returns the program output (or compilation errors) as the RPC response. A front end that runs on Google App Engine. It receives HTTP requests from the client and makes corresponding RPC requests to the back end

Rob Pike 2 December 2013 Introduction From the beginning of the project, Go was designed with tools in mind. Those tools include some of the most iconic pieces of Go technology such as the documentation presentation tool godoc, the code formatting tool gofmt, and the API rewriter gofix. Perhaps most important of all is the go command, the program that automatically installs, builds, and tests Go p

Andrew Gerrand 1 December 2013 We are pleased to announce the release of Go 1.2, the latest stable version of the Go Programming Language. Binary distributions may be downloaded from the usual place or if you prefer to compile from source you should use the release or go1.2 tags. This new release comes nearly seven months after the release of Go 1.1 in May, a much shorter period than the 14 months

Go’s approach to normalization As mentioned in the strings blog post, Go does not guarantee that characters in a string are normalized. However, the go.text packages can compensate. For example, the collate package, which can sort strings in a language-specific way, works correctly even with unnormalized strings. The packages in go.text do not always require normalized input, but in general normal