Chris Hines @[email protected]

Software Engineer, Gopher

[Chris Hines @[email protected] @chris_csguy]

@bitfield https://t.co/gBZ3JrmLKu

[Fatih Arslan @fatih]

My one and only pattern to mock time in Go #golang

[Go @golang]

“Code coverage for Go integration tests” by Than McIntosh — https://t.co/eY5spYnmtM

#golang

[Felix Geisendörfer @felixge]

🐞📢 PSA: Using Go's builtin CPU profiler on macOS (M1) appears to be broken when the workload is interleaved with system calls.

Could anybody with an intel macOS machine try to reproduce this? Thanks 🙏

https://t.co/iai7RnoBQy

[Go @golang]

🎊 Go 1.20 Release Candidate 1 is released!

🏃‍♂️ Run it in dev! Run it in prod! File bugs! https://t.co/Ul1xGhvlkf

📣 Announcement: https://t.co/9zC7AEG4ny

📦 Download: https://t.co/rTk1iN8RNz

#golang

[Chris Hines @[email protected] @chris_csguy]

I've staked out an escape route see ☝️☝️☝️

[Dmitry Vyukov @dvyukov]

Go style guide is awesome on its own, but particularly useful to give references during code reviews:
https://t.co/TzcsWfjBNl
(don't miss Decisions and Best practices sections)

[Go @golang]

🧐 “Thirteen years of Go” by @_rsc

🎉🎂🥳

— https://t.co/Nh6ILAwrk2

#golang

[John Arundel @bitfield]

“You can understand why some get excited about test coverage. It seems to make it possible to boil down the nebulous business of measuring code quality to a single number. But not every change that increases test coverage is necessarily an improvement.”
—The Power of Go: Tests

[Chris Hines @[email protected] @chris_csguy]

@goinggodotnet @FiloSottile For me, learning how git works at the plumbing layer was the mental model I needed to map what the higher level porcelain layer does into sensible ideas I could think about.

[Chris Hines @[email protected] @chris_csguy]

@commaok Does Mathematica count? https://t.co/s1rp9jf1ti

[Damian Gryski @dgryski]

redefining for loop variable semantics

https://t.co/GD17w1CNa3

[Chris Hines @[email protected] @chris_csguy]

Reducing complexity is more powerful than hiding it.

[Chris Hines @[email protected] @chris_csguy]

@felixge It's a shortcoming of the tool. Two issues to take a look at: https://t.co/MZVY1gBHB3 and https://t.co/OKvfLbE4aB.

[Chris Hines @[email protected] @chris_csguy]

@rogpeppe @bitfield @imtheotherbose @khanreaper Since we're specifically talking about one method interfaces here, one bullet from each list is moot, so based on my advice the choice would hinge mostly around statefulness and complexity of expected implementations.

[Chris Hines @[email protected] @chris_csguy]

@rogpeppe @bitfield @imtheotherbose @khanreaper Use function values when:
- Only one behavior
- Typically stateless
- In-line implementations typical

[🇺🇦 Go performance channel @go_perf]

Respecting Memory Limits In Go by @mknyswe (@gopherconeu 💕)

https://t.co/ip1BMyaKqR