An error occurred fetching the project authors.
- 19 Jul, 2019 1 commit
-
-
Jay Conrod authored
Fixes #33149 Change-Id: If9ff24fea6d087b4047a9f6e50f99f449f9b1c52 Reviewed-on: https://go-review.googlesource.com/c/go/+/186618 Run-TryBot: Jay Conrod <jayconrod@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Bryan C. Mills <bcmills@google.com>
-
- 17 Jul, 2019 1 commit
-
-
Alberto Donizetti authored
While it's true that CL 168479 was also backported to 1.12, this is irrelevant for the Go1.13 release notes. Change-Id: I044be69f8f2bc005f58a0d63db05129add15f674 Reviewed-on: https://go-review.googlesource.com/c/go/+/186138Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-
- 16 Jul, 2019 1 commit
-
-
Bryan C. Mills authored
Do not allow a pseudo-version derived from a canonical tag to refer to the same revision as the tag itself. It's unnecessary (because canonical tags already have a total ordering) and confusing (the pseudo-version appears to come after the tag, but actually refers to the exact same revision). Updates #32879 Updates #27173 Change-Id: I02befedbe89c8819bdd93e470783ce63fc813193 Reviewed-on: https://go-review.googlesource.com/c/go/+/184720 Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Jay Conrod <jayconrod@google.com>
-
- 15 Jul, 2019 1 commit
-
-
Filippo Valsorda authored
Updates #32716 Change-Id: Ia0c03918e8f2da4d9824c49c6d4cfca1b0787b0a Reviewed-on: https://go-review.googlesource.com/c/go/+/184102Reviewed-by:
Andrew Bonventre <andybons@golang.org>
-
- 14 Jul, 2019 1 commit
-
-
Alberto Donizetti authored
Change-Id: I465f10533cc76d8160e56bc49eabaf8127ac4e61 Reviewed-on: https://go-review.googlesource.com/c/go/+/186137Reviewed-by:
Andrew Bonventre <andybons@golang.org>
-
- 12 Jul, 2019 1 commit
-
-
Norman B. Lancaster authored
Go 1.14 will no longer run on Native Client (NaCl). Updating the 1.13 release notes to indicate this. See #30439. Fixes #32948 Change-Id: Ia147bb053adc098bd696dbdb01553c23222f8134 Reviewed-on: https://go-review.googlesource.com/c/go/+/185537Reviewed-by:
Andrew Bonventre <andybons@golang.org>
-
- 05 Jul, 2019 1 commit
-
-
Mohit Agarwal authored
- fix link for `Time.Format` - fix closing tag for `go get` - add links for `runtime.Caller`, `runtime.Callers` - remove link for `TypedArrayOf` since it has been removed (CL 177537) Change-Id: I1dc38226e6d91c68fbd2f02c1acfad5327f4ebe8 Reviewed-on: https://go-review.googlesource.com/c/go/+/185038Reviewed-by:
Emmanuel Odeke <emm.odeke@gmail.com>
-
- 03 Jul, 2019 1 commit
-
-
Tobias Klauser authored
Change-Id: I99e76c0c12050289be5b353595eb21fbabe7c01e Reviewed-on: https://go-review.googlesource.com/c/go/+/184597Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-
- 27 Jun, 2019 1 commit
-
-
Diogo Pinela authored
When reading tip.golang.org/doc/go1.13.html, the spec links in the "Changes to the language" section should point to the updated spec, not the old one. Change-Id: I6b13ca0b4c722ed52b84a12a680bece876a4e478 Reviewed-on: https://go-review.googlesource.com/c/go/+/184118Reviewed-by:
Brad Fitzpatrick <bradfitz@golang.org>
-
- 26 Jun, 2019 4 commits
-
-
Bryan C. Mills authored
Looking at the live release notes on tip.golang.org, the Modules section is much more verbose than the other sections. To some extent that's to be expected, but too much detail in the release notes might discourage folks from consulting the actual documentation. Ensure that topics have clear links and omit unnecessary details. Change-Id: I1ccbc1697fccaf7ca7094c606bd11696c46d87f0 Reviewed-on: https://go-review.googlesource.com/c/go/+/183987 Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by:
Jay Conrod <jayconrod@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Jay Conrod authored
Change-Id: I18e2546f89e68e77d6e829acc997851751a44f0c Reviewed-on: https://go-review.googlesource.com/c/go/+/183983 Run-TryBot: Jay Conrod <jayconrod@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Bryan C. Mills <bcmills@google.com>
-
Bryan C. Mills authored
As suggested by thepudds in CL 183630. Also adjust the paragraph to harmonize the transitions between the newly-adjacent paragraphs. Change-Id: Ie85abea946db81804c1995d27be4951d5db6b812 Reviewed-on: https://go-review.googlesource.com/c/go/+/183918Reviewed-by:
Jay Conrod <jayconrod@google.com>
-
Bryan C. Mills authored
Updates #31857 Change-Id: Id0dc66246f768a2c730c67cd7a4a7830547f22a8 Reviewed-on: https://go-review.googlesource.com/c/go/+/183922 Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by:
Jay Conrod <jayconrod@google.com> Reviewed-by:
Katie Hockman <katie@golang.org>
-
- 25 Jun, 2019 6 commits
-
-
Jay Conrod authored
Change-Id: Ieb4a78730a0685627b4730381b72cbd01031c8fa Reviewed-on: https://go-review.googlesource.com/c/go/+/183633 Run-TryBot: Jay Conrod <jayconrod@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Bryan C. Mills <bcmills@google.com>
-
Dmitri Shuralyov authored
Fixup for two typos from CL 183630. Change-Id: I7968a736680e8a6bbd1f4691d443b217702bc190 Reviewed-on: https://go-review.googlesource.com/c/go/+/183843Reviewed-by:
Bryan C. Mills <bcmills@google.com>
-
Bryan C. Mills authored
Change-Id: I99669339b816a3ae56bbe082a8c47ae17e763d71 Reviewed-on: https://go-review.googlesource.com/c/go/+/183632Reviewed-by:
Katie Hockman <katie@golang.org> Reviewed-by:
Jay Conrod <jayconrod@google.com>
-
Bryan C. Mills authored
Change-Id: I0c8c30b40a33763dc34f15d144346eb1a0997df2 Reviewed-on: https://go-review.googlesource.com/c/go/+/183631Reviewed-by:
Jay Conrod <jayconrod@google.com>
-
Bryan C. Mills authored
Also fix up markup in the “Version validation” section to correct indentation on Chrome. Change-Id: Ib930d324567c086bbd0c67b105272bdfcca77b12 Reviewed-on: https://go-review.googlesource.com/c/go/+/183630Reviewed-by:
Jay Conrod <jayconrod@google.com>
-
Andrew authored
Also removes remaining TODOs Change-Id: Id80021b7a64c923c4ebd69fb6e8831a43a76dc72 Reviewed-on: https://go-review.googlesource.com/c/go/+/183625Reviewed-by:
Katie Hockman <katie@golang.org>
-
- 24 Jun, 2019 3 commits
-
-
Filippo Valsorda authored
Change-Id: I80f2b50c8dd3d3f0fea6ed25fa2581786152d470 Reviewed-on: https://go-review.googlesource.com/c/go/+/183621Reviewed-by:
Bryan C. Mills <bcmills@google.com>
-
Ian Lance Taylor authored
Also alphabetize port listing. Change-Id: I4cc552a74856c9955571d721deb6223438c7d856 Reviewed-on: https://go-review.googlesource.com/c/go/+/183637Reviewed-by:
Dmitri Shuralyov <dmitshur@golang.org>
-
Andrew authored
Change-Id: I8c19c6df6fec74dcc8c3bfdc667576ea00e86ec1 Reviewed-on: https://go-review.googlesource.com/c/go/+/183617Reviewed-by:
Katie Hockman <katie@golang.org>
-
- 21 Jun, 2019 3 commits
-
-
Dmitri Shuralyov authored
Updates #30029 Updates #31457 Change-Id: I08414a544615e74afb47f7a10a00f1e22adfd40c Reviewed-on: https://go-review.googlesource.com/c/go/+/182619Reviewed-by:
Katie Hockman <katie@golang.org>
-
Bryan C. Mills authored
Previously, most operations involving pseudo-versions allowed any arbitrary combination of version string and date, and would resolve to the underlying revision (typically a Git commit hash) as long as that revision existed. There are a number of problems with that approach: • The pseudo-version participates in minimal version selection. If its version prefix is inaccurate, the pseudo-version may appear to have higher precedence that the releases that follow it, effectively “pinning” the module to that commit. For release tags, module authors are the ones who make the decision about release tagging; they should also have control over the pseudo-version precedence within their module. • The commit date within the pseudo-version provides a total order among pseudo-versions. If it is not accurate, the pseudo-version will sort into the wrong place relative to other commits with the same version prefix. To address those problems, this change restricts the pseudo-versions that the 'go' command accepts, rendering some previously accepted-but-not-canonical versions invalid. A pseudo-version is now valid only if all of: 1. The tag from which the pseudo-version derives points to the named revision or one of its ancestors as reported by the underlying VCS tool, or the pseudo-version is not derived from any tag (that is, has a "vX.0.0-" prefix before the date string and uses the lowest major version appropriate to the module path). 2. The date string within the pseudo-version matches the UTC timestamp of the revision as reported by the underlying VCS tool. 3. The short name of the revision within the pseudo-version (such as a Git hash prefix) is the same as the short name reported by the underlying cmd/go/internal/modfetch/codehost.Repo. Specifically, if the short name is a SHA-1 prefix, it must use the same number of hex digits (12) as codehost.ShortenSHA1. 4. The pseudo-version includes a '+incompatible' suffix only if it is needed for the corresponding major version, and only if the underlying module does not have a go.mod file. We believe that all releases of the 'go' tool have generated pseudo-versions that meet these constraints. However, a few pseudo-versions edited by hand or generated by third-party tools do not. If we discover invalid-but-benign pseudo-versions in widely-used existing dependencies, we may choose to add a whitelist for those specific path/version combinations. ― To work around invalid dependencies in leaf modules, users may add a 'replace' directive from the invalid version to its valid equivalent. Note that the go command's go.mod parser automatically resolves commit hashes found in 'replace' directives to the appropriate pseudo-versions, so in most cases one can write something like: replace github.com/docker/docker v1.14.0-0.20190319215453-e7b5f7dbe98c => github.com/docker/docker e7b5f7dbe98c and then run any 'go' command (such as 'go list' or 'go mod tidy') to resolve it to an appropriate pseudo-version. Note that the invalid version will still be used in minimal version selection, so this use of 'replace' directives is an incomplete workaround. ― One of the common use cases for higher-than-tagged pseudo-versions is for projects that do parallel development on release branches. For example, if a project cuts a 'v1.2' release branch at v1.2.0, they may want future commits on the main branch to show up as pre-releases for v1.3.0 rather than for v1.2.1 — especially if v1.2.1 is already tagged on the release branch. (On the other hand, a backport of a patch to the v1.2 branch should not show up as a pre-release for v1.3.0.) To address this use-case, module authors can make use of our existing support for pseudo-versions derived from pre-release tags: if the author adds an explicit pre-release tag (such as 'v1.3.0-devel') to the first commit after the branch, then the pseudo-versions for that commit and its descendents will be derived from that tag and will sort appropriately in version selection. ― Updates #27171 Fixes #29262 Fixes #27173 Fixes #32662 Fixes #32695 Change-Id: I0d50a538b6fdb0d3080aca9c9c3df1040da1b329 Reviewed-on: https://go-review.googlesource.com/c/go/+/181881 Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by:
Jay Conrod <jayconrod@google.com>
-
Robert Griesemer authored
Change-Id: I2230a97c681406f248b7f2fff45dd80a4b54a4b3 Reviewed-on: https://go-review.googlesource.com/c/go/+/183357Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-
- 19 Jun, 2019 3 commits
-
-
Andrew authored
Change-Id: I4ddbe22061579383ca47e14d0b64a74365fb3d19 Reviewed-on: https://go-review.googlesource.com/c/go/+/182797Reviewed-by:
Katie Hockman <katie@golang.org>
-
Austin Clements authored
Change-Id: I6338bba2a86fb27421f91203a04b39830bae1e52 Reviewed-on: https://go-review.googlesource.com/c/go/+/182800Reviewed-by:
Cherry Zhang <cherryyz@google.com> Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-
Robert Griesemer authored
Change-Id: I17b156e77f279e1387ad27ab0e41ae8f50c9a325 Reviewed-on: https://go-review.googlesource.com/c/go/+/182857Reviewed-by:
Ian Lance Taylor <iant@golang.org> Reviewed-by:
Austin Clements <austin@google.com>
-
- 18 Jun, 2019 4 commits
-
-
Filippo Valsorda authored
Change-Id: I05d4ff3d3a31f56c9ceebdaceb39535a1351b26a Reviewed-on: https://go-review.googlesource.com/c/go/+/182701Reviewed-by:
Andrew Bonventre <andybons@golang.org>
-
Andrew authored
Change-Id: I54dc8afc33d6f8946d2c79b0339118fa3710a688 Reviewed-on: https://go-review.googlesource.com/c/go/+/182618Reviewed-by:
Bryan C. Mills <bcmills@google.com>
-
Austin Clements authored
Change-Id: Icc5083a3de0c6b737bfc20b573ed785651910148 Reviewed-on: https://go-review.googlesource.com/c/go/+/182461Reviewed-by:
Andrew Bonventre <andybons@golang.org>
-
Josh Bleecher Snyder authored
There is a subtle distinction between a value *being* the zero value vs being *equal to* the zero value. This was discussed at length in #31450. Using "a zero value" in the docs suggests that there may be more than zero value. That is possible on the "equal to zero value" reading, but not the "is zero" reading that we selected for the semantics of IsZero. This change attempts to prevent any confusion on this front by switching to "the zero value" in the documentation. And while we're here, eliminate a double-space. (Darn macbook keyboards.) Change-Id: Iaa02ba297438793f5a90be9919a4d53baef92f8e Reviewed-on: https://go-review.googlesource.com/c/go/+/182617 Run-TryBot: Josh Bleecher Snyder <josharian@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Brad Fitzpatrick <bradfitz@golang.org>
-
- 17 Jun, 2019 1 commit
-
-
Keith Randall authored
Write release notes for a few reflect, runtime, and syscall changes. The init randomization has been reverted. Change-Id: Idae481ca015e325eb7302abaa15b2792312f4c32 Reviewed-on: https://go-review.googlesource.com/c/go/+/181577Reviewed-by:
Austin Clements <austin@google.com>
-
- 14 Jun, 2019 3 commits
-
-
Katie Hockman authored
Change-Id: I0ee4b4f0211cd12803ab33976669350d9dd615f3 Reviewed-on: https://go-review.googlesource.com/c/go/+/181944Reviewed-by:
Andrew Bonventre <andybons@golang.org>
-
Julie authored
Change-Id: Ifd330053094c172b7dcd9086da173289efc7f9b8 Reviewed-on: https://go-review.googlesource.com/c/go/+/181942Reviewed-by:
Katie Hockman <katie@golang.org> Reviewed-by:
Andrew Bonventre <andybons@golang.org>
-
Julie authored
Change-Id: I4c52d9bcf941810dbdfdd39e7f339c8283d6bcc7 Reviewed-on: https://go-review.googlesource.com/c/go/+/181937Reviewed-by:
Katie Hockman <katie@golang.org>
-
- 13 Jun, 2019 4 commits
-
-
Katie Hockman authored
Change-Id: I2a0bd295ad9737581d149a7165191b878ae2acda Reviewed-on: https://go-review.googlesource.com/c/go/+/181880Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-
Julie authored
Change-Id: I71a6816f54f8ad0f8531bb3f9de552fd136a0ed4 Reviewed-on: https://go-review.googlesource.com/c/go/+/181943Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-
Julie authored
Change-Id: Ifdc3c5b840e6833f14c8e52948e45d5faa5a0615 Reviewed-on: https://go-review.googlesource.com/c/go/+/181940Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-
Dmitri Shuralyov authored
This change makes the release notes for Go 1.13 more complete by mentioning a new function in the os package. Change-Id: I0d637fd70ff6d14782bbfb7c13985a0f83b19d6d Reviewed-on: https://go-review.googlesource.com/c/go/+/181945Reviewed-by:
Ian Lance Taylor <iant@golang.org>
-