@jmoiron @Robinson_Music @buckwilson http://t.co/mTk0gmnBUz experimental artist, lots of textures/layering, can be a challenging listen
@jmoiron @wefreema ah! feel free to email me at length :) We'll have to have an east coast go/sql meetup sometime!
@jmoiron this document on haskell type classes is about the size of the entire #golang spec http://t.co/j9DS6FSPvp
@jmoiron RT @bradfitz: "It's important to pay attention to all the words in the Go docs. They don't repeat themselves for emphasis." -- @xaprb #goph…
@jmoiron RT @gniemeyer: Great community vibe at @GopherCon. Many kudos to @bketelsen and @erikstmartin for the organization.
@jmoiron @buckwilson mmm, nice. been liking this for rainy time glass-o-scotch: http://t.co/9eZejx5QTa
@jmoiron TIL that the unix epoch repeats on leap seconds, so e % 86400 will always give you a midnight. http://t.co/gdVMfPeoyT
@jmoiron @Ed_Forson definitely check out http://t.co/QWkuCQKDlU to learn more about what Go data structures look like in memory
@jmoiron @Ed_Forson map[string]struct{} is the actual type. You can use struct definitions inline, this one is just empty.
@jmoiron @Ed_Forson i explain a little here: http://t.co/coDRjksyXr also, struct{} is a type, an inline empty struct, it is 0-byte
@jmoiron @jamwt planning to pretty soon. Compress perf still poor; does a big worst case alloc up front, like python. Trying to fix that first.
@jmoiron @Ed_Forson benches compared map[string]struct{} to map[int]struct{}; needed the str, so used map[int]*Metric (these are types, not literals)
@jmoiron @Ed_Forson structs are a compile time thing, there's no header, so struct{} is a 0-byte type. A pointer is 1 word, strings are 2.