Go tooling essentials
golang.rakyll.org
golang.rakyll.org
For example, to disable compiler optimizations and inlining,
you can use the following the gcflags.
$ go build -gcflags="-N -I"
It should be `-l` and not `-I`, such that it reads:
$ go build -gcflags="-N -l"seeing examples of why you might want to use or remember flag/options is great.
I should revisit the docs for things like the old core gnu stuff to see what gems I've overlooked.
I wouldn't class the article title misleading enough to warrant editorialisation. So this submission is following HN guidelines.
I will never complain about HN titles again because people just can't understand that both HN titles, and article titles can change quickly. It's the nth time I mention that the title is wrong at that particular time, and instead of getting a "thanks" and all I get are downvotes by people that don't realise that either the title of the submission or the title of the article has changed in the meantime.
1) Your comment is meta. Meta comments - however useful - should be below all comments discussing article content. In some cases we downvote if it happened to bubble up.
2) When a point is no longer relevant, it makes sense to push it to the bottom of the stack. That is not a judgment on its merits.
> I will never complain about HN titles again because people just can't understand that both HN titles
Have a little more self-confidence about your contributions. If they're useful, just walk away knowing you did the right thing. You don't need to defend yourself as the veracity of it will make itself known given time.
But generally, I do wish fewer people moaned about HN titles. Even when the title matches the article, people often moan about it's grammer. In fact there was one submission last week where more people were discussing the title than were discussing the article. However I do appreciate the irony that I'm contributing to my complaint by discussing it like I am :)