So what's happening underneath that allows for this kind of speedup while still using reflection? Since it still uses reflection, what would it take to get something like this in stdlib? A much faster implementation would probably be a benefit to many.
I'm not sure I understand. This approach seems complicated and prone to issues as the author mentioned. Why not implement this as a middleware and simply emit those metrics from there, to stdout, your monitoring system or add them to a context?
Could someone remove the excessive tagging? Tagging something as go and golang on golangnews seems rather unnecessary and adds no value. Hack and hacking are pretty much the same thing too, one would suffice.
This is probably the best introductory post I've read on the topic of pointers. I really like how it shows the stack and stack frames to explain what's going on.
The answer is "no", boilerplate isn't always bad. Don't really need to read the article for that though. That said, the article is an interesting read.
This needs a [2015] addendum in the title. A number of the issues the author raises in the end have or are currently being addressed.
So what's happening underneath that allows for this kind of speedup while still using reflection? Since it still uses reflection, what would it take to get something like this in stdlib? A much faster implementation would probably be a benefit to many.
A few questions, since the announcement is very short on any details from my point of view:
I'm not sure I understand. This approach seems complicated and prone to issues as the author mentioned. Why not implement this as a middleware and simply emit those metrics from there, to stdout, your monitoring system or add them to a context?
As cool as this is, since this is Golang News it probably shouldn't be here if it doesn't involve Go? It's already on the front page of HN.
Could someone remove the excessive tagging? Tagging something as go and golang on golangnews seems rather unnecessary and adds no value. Hack and hacking are pretty much the same thing too, one would suffice.
This is probably the best introductory post I've read on the topic of pointers. I really like how it shows the stack and stack frames to explain what's going on.
The answer is "no", boilerplate isn't always bad. Don't really need to read the article for that though. That said, the article is an interesting read.