[
https://issues.apache.org/jira/browse/THRIFT-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090063#comment-16090063
]
ASF GitHub Bot commented on THRIFT-4236:
----------------------------------------
GitHub user taozle opened a pull request:
https://github.com/apache/thrift/pull/1309
Use build tags to support context.
As the comment in https://issues.apache.org/jira/browse/THRIFT-4236, this
PR use build tags to support context in go1.7 above.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/taozle/thrift context
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/thrift/pull/1309.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1309
----
commit 0df5965eb2a35793f19de1b2696e3c4afb6b5132
Author: taozle <[email protected]>
Date: 2017-07-17T16:40:42Z
Use build tags to support context.
----
> Support context in go generated code.
> -------------------------------------
>
> Key: THRIFT-4236
> URL: https://issues.apache.org/jira/browse/THRIFT-4236
> Project: Thrift
> Issue Type: Improvement
> Components: Go - Compiler, Go - Library
> Reporter: taozle
> Assignee: taozle
> Fix For: 0.11.0
>
>
> Since context is widely used in go's community, and there is lots of
> advantage to use context such as control timeout, carry extra info in one
> request etc, so is there any plan for this? i just searched the issues but
> didn't find anything about this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
