qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-14 22:50:27 -07:00
Code Releases Activity
1443a3ea1e
go/doc/next/3-tools.md

13 lines
494 B
Markdown
Raw Normal View History

doc: initialize next directory for Go 1.24 Following the "For the release team" steps in README: cd doc cp -R initial/ next $EDITOR next/1-intro.md Dropped '*' from the cp -R command to avoid needing to create an empty next directory with a separate command. For #68545. For #67586. Change-Id: I25215bc35a043e0f26d4a86ffe66eb3c26348fef Reviewed-on: https://go-review.googlesource.com/c/go/+/600177 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Cherry Mui <cherryyz@google.com>
2024-07-22 10:44:49 -06:00
## Tools {#tools}
### Go command {#go-command}
### Cgo {#cgo}
cmd/cgo: error on multiple incompatible function declarations When there are multiple declarations of a function, ensure that those declarations at least agree on the size/alignment of arguments and return values. It's hard to be stricter given existing code and situations where arguments differ only by typedefs. For instance: int usleep(unsigned); int usleep(useconds_t); Fixes #67699. Change-Id: I3b4b17afee92b55f9e712b4590ec608ab1f7ac91 Reviewed-on: https://go-review.googlesource.com/c/go/+/588977 Auto-Submit: Keith Randall <khr@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Keith Randall <khr@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com>
2024-05-29 20:37:43 -06:00
Cgo currently refuses to compile calls to a C function which has multiple
incompatible declarations. For instance, if `f` is declared as both `void f(int)`
and `void f(double)`, cgo will report an error instead of possibly generating an
incorrect call sequence for `f(0)`. New in this release is a better detector for
this error condition when the incompatible declarations appear in different
doc/next: use relative link to Go issue The Go release notes are served on multiple domains (go.dev, golang.google.cn, tip.golang.org, localhost:8080 and so on), so links pointing to the Go website itself need to be relative to work in all those contexts. Caught by a test in x/website. The next CL adds the same test to this repository so these kinds of problems are caught sooner and with less friction. For #68545. Fixes #68575. Change-Id: I08056b98968c77a1d0ed93b63fccfbe41274ec8f Reviewed-on: https://go-review.googlesource.com/c/go/+/600656 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Ian Lance Taylor <iant@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
2024-07-24 11:30:28 -06:00
files. See [#67699](/issue/67699).
Copy Permalink