Github user dcelasun commented on the issue:
https://github.com/apache/thrift/pull/1382
> I don't think we can unilaterally require go 1.9 at this point without
causing some pain, but I'm not sure.
This change doesn't effect the user, it's only needed for the tests. Though
if you still think we shouldn't do it, I can change the tests to use older
APIs. I didn't want to touch it since I didn't write the original patch.
> It looks like this may not be backwards compatible with existing code -
is there any way to put in an adapter that would allow existing code to
continue working?
I don't think so. Several interfaces had to change since what used to be
returned from generated methods is now returned from the library.
Good news is the changes are limited to client, server and protocol
interfaces (they don't affect the signature for RPCs) so updating to 0.11
should be a few lines of change (initializing the server/client) for most
people.
Just to make sure, I'll update a real application to this patch and post my
experiences here.
---
