rkravchik · February 22, 2018 12:40
diff --git a/sync.Pool.txt b/sync.Pool.txt
 https://github.com/golang/go/issues/8232#issuecomment-66096118

 Put another way, sync.Pool is for answering the question "how do I decide when to drop
 this cached thing that otherwise would never die". The suggestion here is to use it to
 answer the question "how can I make this thing fast". That's a mistake, even if the
 implementation can satisfy both today. If it starts getting used for these two different
 things, then we will not be able to change it, because optimizing for one case will hurt
 the other.

 Russ Cox
	https://github.com/golang/go/issues/8232#issuecomment-66096118

	Put another way, sync.Pool is for answering the question "how do I decide when to drop
	this cached thing that otherwise would never die". The suggestion here is to use it to
	answer the question "how can I make this thing fast". That's a mistake, even if the
	implementation can satisfy both today. If it starts getting used for these two different
	things, then we will not be able to change it, because optimizing for one case will hurt
	the other.

	Russ Cox