kingecg
/
go-cache
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Changed the line about serialization to avoid confusion. We do do that now (via Save), but not in the way this referred to.

This commit is contained in:
Patrick Mylund Nielsen 2012-01-29 03:45:11 +01:00
parent 16b8921ca2
commit 88f8307726
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README
View File

@ -63,10 +63,10 @@ downtime quickly.
} }
// If you store a reference type like a pointer, slice, map or channel, you // If you store a reference type like a pointer, slice, map or channel, you
// do not need to run Set if you modify the underlying data. The cache does // do not need to run Set if you modify the underlying data. The cached
// not serialize its data, so if you modify a struct whose pointer you've // reference points to the same memory, so if you modify a struct whose
// stored in the cache, retrieving that pointer with Get will point you to // pointer you've stored in the cache, retrieving that pointer with Get will
// the same data: // point you to the same data:
foo := &MyStruct{Num: 1} foo := &MyStruct{Num: 1}
c.Set("foo", foo, 0) c.Set("foo", foo, 0)
... ...