Results 599 comments of Wes McNamee

for reference, here's the go playground link, and the output screenshot https://play.golang.org/p/iTnyFO4ML26 ![image](https://user-images.githubusercontent.com/903488/85970415-46523800-b97f-11ea-81bb-8e6874f1fb02.png)

@dolmen yep I already looked at uniseg, and it doesn't provide the right information

You can kinda see some of the problems I'm trying to solve... it seems not even all monospaced fonts are made equally. From the github code view, you can see...

well, I might have landed on something interesting... ``` package main import ( "fmt" "strings" // "unicode/utf8" "github.com/mattn/go-runewidth" ) // aligns to 5 characters func valuePaddingPredictor(val string) string { runeWidth...

I agree with this. I read the readme, and the first and only question I had was "what should I say instead?" Some of the phrases that mentioned to stay...

Just a refresher comment, I have plans to submit at least a PR for this. I like the idea of having etiquette like this be out in the open instead...

Well I'm looking to execute from a different directory without actually changing my current directory, especially as os.chdir is going cause problems if I do any sort of parallelism/threading.

Your example is the functional options API pattern. It's what I use too. It's very good.

That's the one! A really fantastic post. I love the flexibility it provides, and enables you to add functionality to an API without changing the function signatures.