#golang performance tip: If your constructor returns an io.Writer (instead of a concrete type), the compiler can't prove that Write(p) calls don't retain p, so p escapes to the heap! (Same goes for other interfaces, obv)
Show this thread
Try benchmarking a raw (*os.File).Write vs assigning the file to an io.Writer first.
Just another example of how abstractions don't come for free. 
-
-
There are other good reasons for the "accept interfaces, return structs" idiom, but this one is my pet peeve
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.