Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(10)

Issue 7303064: code review 7303064: spec: clarify that any unsafe.Pointer type is okay in c... (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 4 months ago by rsc
Modified:
12 years, 4 months ago
Reviewers:
CC:
golang-dev, r
Visibility:
Public.

Description

spec: clarify that any unsafe.Pointer type is okay in conversion The spec is not clear about whether this is allowed or not, but both compilers allow it, because the reflect implementation takes advantage of it. Document current behavior. Fixes issue 4679.

Patch Set 1 #

Patch Set 2 : diff -r e8eb2c8d5ce1 https://code.google.com/p/go/ #

Patch Set 3 : diff -r e8eb2c8d5ce1 https://code.google.com/p/go/ #

Patch Set 4 : diff -r 5c213525c4b5 https://code.google.com/p/go/ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+12 lines, -3 lines) Patch
M doc/go_spec.html View 1 2 3 1 chunk +12 lines, -3 lines 0 comments Download

Messages

Total messages: 3
rsc
Hello golang-dev@googlegroups.com, I'd like you to review this change to https://code.google.com/p/go/
12 years, 4 months ago (2013-02-09 19:32:38 UTC) #1
r
LGTM
12 years, 4 months ago (2013-02-09 21:14:06 UTC) #2
rsc
12 years, 4 months ago (2013-02-09 22:36:38 UTC) #3
*** Submitted as https://code.google.com/p/go/source/detail?r=a44171137af8 ***

spec: clarify that any unsafe.Pointer type is okay in conversion

The spec is not clear about whether this is allowed or not,
but both compilers allow it, because the reflect implementation
takes advantage of it. Document current behavior.

Fixes issue 4679.

R=golang-dev, r
CC=golang-dev
https://codereview.appspot.com/7303064
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b