arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sutou Kouhei <...@clear-code.com>
Subject Re: [DISCUSS] Result vs Status
Date Sat, 05 Oct 2019 11:49:34 GMT
Hi,

In <21183bb1-813f-b35b-b391-3f52ef2e62c9@python.org>
  "Re: [DISCUSS] Result vs Status" on Sat, 5 Oct 2019 12:23:05 +0200,
  Antoine Pitrou <antoine@python.org> wrote:

>> OK, so what  could more context be provided on:
>> 
>>> From the discussion in the sync call, it seems reasonable to require that:
>>> Public APIs which are likely to be directly wrapped in a binding should not
>>> use Result<> to the exclusion of Status. An equivalent Status API should
>>> always be provided for ease of binding.
> 
> I don't know, sorry :-) I wasn't on the sync call.


We don't need Status API for bindings. We already use
complex types such as std::shared_ptr in our API. Bindings
need C++ feature for complex types. So we don't need to care
about Result<> or Status.


Thanks,
--
kou

Mime
View raw message