delta/go-git.git/src/unsafe, branch dev.typeparams

spec, unsafe: clarify unsafe.Slice docs

2021-07-02T19:26:52+00:00

For #19367

Change-Id: If0ff8ddba3b6b48e2e198cf3653e73284c7572a3
Reviewed-on: https://go-review.googlesource.com/c/go/+/332409
Trust: Ian Lance Taylor 
Reviewed-by: Matthew Dempsky 
Reviewed-by: Robert Griesemer 
Reviewed-by: Keith Randall

spec: change unsafe.Slice((*T)(nil), 0) to return []T(nil)

2021-06-28T23:31:05+00:00

Updates #46742.

Change-Id: I044933a657cd1a5cdb29863e49751df5fe9c258a
Reviewed-on: https://go-review.googlesource.com/c/go/+/331069
Run-TryBot: Matthew Dempsky 
Trust: Matthew Dempsky 
Trust: Robert Griesemer 
Reviewed-by: Robert Griesemer

spec: add unsafe.Add and unsafe.Slice

2021-04-22T22:03:10+00:00

Updates #19367.
Updates #40481.

Change-Id: I578066ad68d2cd6bea50df1a534cf799e4404a7f
Reviewed-on: https://go-review.googlesource.com/c/go/+/312212
Trust: Matthew Dempsky 
Trust: Robert Griesemer 
Reviewed-by: Ian Lance Taylor 
Reviewed-by: Rob Pike 
Reviewed-by: Robert Griesemer 
Reviewed-by: Russ Cox

cmd/compile: assume unsafe pointer arithmetic generates non-nil results

2018-11-14T21:01:36+00:00

I've never seen a case where unsafe arithmetic is used to generate a nil.
(Something like var x uintptr; unsafe.Pointer(x - x).)
We can assume that if someone is doing arithmetic with pointers, the
result will be non-nil. Our unsafe rules already forbid this, although
we should be more explicit.

RELNOTE=It is invalid to convert a nil unsafe.Pointer to uintptr and back, with arithmetic.
(This was already invalid, but this statement has been added for clarification.)

Fixes #27180

Change-Id: I1880b7725a9fd99e4613799930fdad9aaa99e8f0
Reviewed-on: https://go-review.googlesource.com/c/146058
Reviewed-by: Austin Clements

unsafe: document that Alignof, Offsetof, and Sizeof return a constant

2018-10-11T02:32:20+00:00

Nothing is changing but the documentation, which did not mention
this property of these functions.

Fixes #27587.

Change-Id: I75bcee4a1dd9ec8cd82826c9a6e02ba7d599f719
Reviewed-on: https://go-review.googlesource.com/c/141377
Reviewed-by: Brad Fitzpatrick

unsafe: fix reference to string header

2018-02-26T18:35:46+00:00

Fixes #24115

Change-Id: I89d3d5a9c0916fd2e21fe5930549c4129de8ab48
Reviewed-on: https://go-review.googlesource.com/96983
Reviewed-by: Giovanni Bajo 
Reviewed-by: Brad Fitzpatrick

all: remove some double spaces from comments

2017-08-26T15:09:09+00:00

Went mainly for the ones that make no sense, such as the ones
mid-sentence or after commas.

Change-Id: Ie245d2c19cc7428a06295635cf6a9482ade25ff0
Reviewed-on: https://go-review.googlesource.com/57293
Reviewed-by: Ian Lance Taylor 
Run-TryBot: Daniel Martí 
TryBot-Result: Gobot Gobot

unsafe: remove incorrect type conversion in docs

2016-11-07T18:54:14+00:00

Fixes #17818.

Change-Id: Id7242b0bdd5e1db254b44ae29900fc4f3362c743
Reviewed-on: https://go-review.googlesource.com/32828
Reviewed-by: Brad Fitzpatrick

unsafe: document use of &^ to round/align pointers

2016-08-18T16:45:17+00:00

Follow-up to CL 27156

Change-Id: I4f1cfced2dced9c9fc8a05bbc00ec4229e85c5c9
Reviewed-on: https://go-review.googlesource.com/27314
Reviewed-by: Ian Lance Taylor

all: single space after period.

2016-03-02T00:13:47+00:00

The tree's pretty inconsistent about single space vs double space
after a period in documentation. Make it consistently a single space,
per earlier decisions. This means contributors won't be confused by
misleading precedence.

This CL doesn't use go/doc to parse. It only addresses // comments.
It was generated with:

$ perl -i -npe 's,^(\s*// .+[a-z]\.)  +([A-Z]),$1 $2,' $(git grep -l -E '^\s*//(.+\.)  +([A-Z])')
$ go test go/doc -update

Change-Id: Iccdb99c37c797ef1f804a94b22ba5ee4b500c4f7
Reviewed-on: https://go-review.googlesource.com/20022
Reviewed-by: Rob Pike 
Reviewed-by: Dave Day 
Run-TryBot: Brad Fitzpatrick 
TryBot-Result: Gobot Gobot