_content/doc/go1.26.md: add io.ReadAll and fmt.Errorf optimizations We certainly don't need to document every optimization in the release notes, but these two CLs I had sent seem more worthwhile to include given people empirically were avoiding two relatively fundamental APIs over performance concerns. For io.ReadAll, people were for example posting things like "io.ReadAll is documented to be inefficient" on different issues on various open source projects. See https://go.dev/cl/722500 for additional details. For fmt.Errorf, I believe fmt.Errorf("foo") has been considered by the core Go team to be perfectly fine, but that did not stop a steady drip of CLs seeking to remove instances for performance reasons, or linters that complained while citing performance, and so on. See https://go.dev/cl/708836 for some additional discussion. Also, it's nice when the simpler and more idiomatic user code has the same or better performance than more complex code. Change-Id: I409b495f1cc514588fb2160a7f36cd9bf1ce03e5 Reviewed-on: https://go-review.googlesource.com/c/website/+/729261 Reviewed-by: David Chase <drchase@google.com> Reviewed-by: Keith Randall <khr@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Keith Randall <khr@golang.org> Auto-Submit: David Chase <drchase@google.com> Reviewed-by: Sean Liao <sean@liao.dev> Reviewed-by: Keith Randall <khr@golang.org>
This repo holds content and serving programs for the go.dev and golang.org web sites.
Content is in _content/ (go.dev) and tour/ (go.dev/tour). Server code is in cmd/ and internal/.
To run the combined go.dev+golang.org server to preview local content changes, use:
go run ./cmd/golangorg
The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for admin.golang.org and google.golang.org. (They do not use the _content/ directories.)
Each command directory has its own README.md explaining deployment.
This repository uses eslint to format JS and TS files, and stylelint to format CSS files.
See also:
It is encouraged that all JS, TS, and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npm install./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
TypeScript files served from _content are transformed into JavaScript. Reference .ts files in html templates as module code.
<script type="module" src="/ts/filename.ts">
Write unit tests for TypeScript code using the jest testing framework.
./npx jest [TestPathPattern]
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
The git repository is https://go.googlesource.com/website.
The main issue tracker for the website repository is located at https://go.dev/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.