hash/maphash: mention that hash values do not persist in package docs

Updates golang#36878 Fixes golang#37040 Change-Id: Ib0bd21481e5d9c3b3966c116966ecfe071243a24 Reviewed-on: https://go-review.googlesource.com/c/go/+/218297 Reviewed-by: Keith Randall <[email protected]> Reviewed-by: Emmanuel Odeke <[email protected]>
pengfei-su · Feb 11, 2020 · 1c241d2 · 1c241d2
1 parent 25da21d
commit 1c241d2
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/doc/go1.14.html b/doc/go1.14.html
@@ -616,6 +616,10 @@ <h3 id="minor_library_changes">Minor changes to the library</h3>
     <p>
       The hash functions are collision-resistant but not cryptographically secure.
     </p>
+    <p>
+      The hash value of a given byte sequence is consistent within a
+      single process, but will be different in different processes.
+    </p>
   </dd>
 </dl><!-- hash/maphash -->
 

diff --git a/src/hash/maphash/maphash.go b/src/hash/maphash/maphash.go
@@ -9,6 +9,9 @@
 //
 // The hash functions are collision-resistant but not cryptographically secure.
 // (See crypto/sha256 and crypto/sha512 for cryptographic use.)
+//
+// The hash value of a given byte sequence is consistent within a
+// single process, but will be different in different processes.
 package maphash
 
 import "unsafe"