Done, see https://issues.apache.org/jira/browse/ARROW-2522
Le 28/04/2018 à 02:01, Wes McKinney a écrit :
> Yes, I'd say let's definitely bump the SO version with each major
> release. Is there a JIRA for this already? If not let's create one
>
> On Tue, Apr 24, 2018 at 2:02 PM, Antoine Pitrou
Yes, I'd say let's definitely bump the SO version with each major
release. Is there a JIRA for this already? If not let's create one
On Tue, Apr 24, 2018 at 2:02 PM, Antoine Pitrou wrote:
>
> Le 24/04/2018 à 19:58, Wes McKinney a écrit :
>>
>> In summary, until the Arrow developer group grows sig
Le 24/04/2018 à 19:58, Wes McKinney a écrit :
>
> In summary, until the Arrow developer group grows significantly
> larger, I think we should expect the users of these libraries to "live
> at HEAD". I do think we should make ABI changes transparent and
> well-documented so the pain is minimized.
Personally, I am not really in favor of ABI stability in the short
term for a few reasons
* We don't have enough maintainers as is to keep up with the
development flow in the project
* It will may harm forward progress in the project's design. Because
the development team is so small and there ar
Hi Uwe,
Le 19/04/2018 à 18:42, Uwe L. Korn a écrit :
>> 1) are we ok with paying the cost of pimpls? (mostly the indirection
>> cost I guess, and the fact that we can't have inline methods/accessors
>> anymore)
>
> I'm not sure about how much of the cost we're ready to pay. There is a
> certain
Hello Antoine,
comments inline.
On Thu, Apr 19, 2018, at 2:21 PM, Antoine Pitrou wrote:
> On Thu, 19 Apr 2018 07:17:34 -0400
> Alex Hagerman wrote:
> > Notes from yesterdays sync call:
> >
> > Uwe suggested adding in checks for the C++ ABI to detect breaking
> > changes. Discussed adding this
Thanks for the note! Sorry my calendar doesn’t pop up so I missed the sync.
On Thu, Apr 19, 2018 at 8:22 AM Antoine Pitrou wrote:
> On Thu, 19 Apr 2018 07:17:34 -0400
> Alex Hagerman wrote:
> > Notes from yesterdays sync call:
> >
> > Uwe suggested adding in checks for the C++ ABI to detect bre
On Thu, 19 Apr 2018 07:17:34 -0400
Alex Hagerman wrote:
> Notes from yesterdays sync call:
>
> Uwe suggested adding in checks for the C++ ABI to detect breaking
> changes. Discussed adding this to a CI build job daily.
>
> Wes asked if certain C++ symbols could be marked experimental when
> pe
