diff --git a/doc/go1.3.html b/doc/go1.3.html index 4c59f212cd..d98cdf629f 100644 --- a/doc/go1.3.html +++ b/doc/go1.3.html @@ -136,17 +136,17 @@ contain pointers and other values do not. This assumption is fundamental to the precise behavior of both stack expansion and garbage collection. Programs that use package unsafe -to store uintptrs in pointer values are illegal and will crash if the runtime detects the behavior. +to store integers in pointer-typed values are illegal and will crash if the runtime detects the behavior. Programs that use package unsafe to store pointers -in uintptr values are also illegal but more difficult to diagnose during execution. +in integer-typed values are also illegal but more difficult to diagnose during execution. Because the pointers are hidden from the runtime, a stack expansion or garbage collection may reclaim the memory they point at, creating dangling pointers.

-Updating: Code that converts a uintptr value stored in memory -to unsafe.Pointer is illegal and must be rewritten. +Updating: Code that uses unsafe.Pointer to convert +an integer-typed value held in memory into a pointer is illegal and must be rewritten. Such code can be identified by go vet.