Just came here to post this, thanks for posting. I've moved some text into the description because the title was too long. This looks really interesting, the description of how it works is pretty scary, requiring inserting code into your file and modifying the file in place (why not a copy?), but I guess you'd use it to explore possibilities in existing code.
Looks interesting thanks for posting. It would be nice to see this using one of the go databases available, instead of sqlite, as then it wouldn't need cgo. Given the simplicity of the data, it shouldn't be too hard.
This has no relation to the gotime podcast of course.
Interesting article, but there is a bug open to fix this now, and it will probably be addressed in the compiler soon - since it makes the code more complex to read I don't think this is really a net win. I don't like the way they are combining naked returns and named return values at the top of the function here, they could at least explicitly return the value.