amclay

Also running into this issue with go 1.8

@Sentimentron Do you have plans to support/revisit this at a later date still?