[
https://issues.apache.org/jira/browse/THRIFT-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032434#comment-15032434
]
Jens Geyer commented on THRIFT-3459:
------------------------------------
{quote}
Thrift can use $SOME_LIBRARY
{quote}
As long as we don't add any dependencies that are *not* optional, that's fine.
If this is going to add a hard dependency to whatever library and this is by no
means convertible into something that can be added optionally, I'm not so sure
if we really want this. Speaking about Thrift in general, we try to keep it
free from hard dependencies.
If this can be made optional in some way, either by just optionally adding it
to the current D project, or (in the case where Thrift compiler support is
needed) to bind this additional dependency to an compiler parameter (like
{{thrift -gen d:add_support_for_XYZ}}) and some majority of users wants this,
e.g. because XYZ is state of the art, that's a different thing.
Could you please elaborate somewhat more about why you think this is a good
addition?
> integrate with vibe-d (fibers) framework
> ----------------------------------------
>
> Key: THRIFT-3459
> URL: https://issues.apache.org/jira/browse/THRIFT-3459
> Project: Thrift
> Issue Type: Improvement
> Components: D - Library
> Reporter: Tolstokulakov Nikolay
>
> Currently it is necessary to use async client inside vibe-d application.
> Thrift can use vibe-d IO library and it eliminates unnecessary multi thread
> communications.
> Sample from ddb project (option -version=Have_vibe_d):
> https://github.com/pszturmaj/ddb/blob/master/source/ddb/postgres.d
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
