+1
El mar, 20 may 2025 a las 4:14, Neal Richardson (<
neal.p.richard...@gmail.com>) escribió:
> +1
>
> On Mon, May 19, 2025 at 10:06 PM Ruoxi Sun wrote:
>
> > +1
> >
> > *Regards,*
> > *Rossi SUN*
> >
> >
> > On Mon, May 19, 2025 at 6:48 PM Bryce Mecum
> wrote:
> >
> > > +1
> > >
> > > On Mon,
+1 (non-binding)
Best,
Xuwei Fu
Antoine Pitrou 于2025年5月20日周二 00:14写道：
>
> Hello,
>
> I am proposing that we switch Arrow C++ to require C++20.
>
> C++20 will offer support for more C++ language and standard library
> features, such as:
>
> - concepts
> - generic lambdas with explicit type param
+1
On Tue, May 20, 2025 at 7:09 AM Ruoxi Sun wrote:
> > Is it fair to say most users of Arrow C++ do that via Python/R or shared
> libraries? Making the migration to a recent C++ standard relatively safe?
>
> I would say so. For some C++ dependents I know of, they either don't depend
> on very r
+1
On Mon, May 19, 2025 at 10:06 PM Ruoxi Sun wrote:
> +1
>
> *Regards,*
> *Rossi SUN*
>
>
> On Mon, May 19, 2025 at 6:48 PM Bryce Mecum wrote:
>
> > +1
> >
> > On Mon, May 19, 2025 at 6:24 PM Sutou Kouhei wrote:
> > >
> > > Hi,
> > >
> > > I would like to propose splitting the Swift implement
+1
*Regards,*
*Rossi SUN*
On Mon, May 19, 2025 at 6:48 PM Bryce Mecum wrote:
> +1
>
> On Mon, May 19, 2025 at 6:24 PM Sutou Kouhei wrote:
> >
> > Hi,
> >
> > I would like to propose splitting the Swift implementation
> > to its own repository.
> >
> > Motivation:
> >
> > * We want to make the
+1
On Mon, May 19, 2025 at 6:24 PM Sutou Kouhei wrote:
>
> Hi,
>
> I would like to propose splitting the Swift implementation
> to its own repository.
>
> Motivation:
>
> * We want to make the Swift implementation Swift Package
> Manager compatible.
> * It requires a top-level Package.swift.
+1
In <20250520.102433.1649746168986082120@clear-code.com>
"[VOTE][Swift] Split Swift to separated repository" on Tue, 20 May 2025
10:24:33 +0900 (JST),
Sutou Kouhei wrote:
> Hi,
>
> I would like to propose splitting the Swift implementation
> to its own repository.
>
> Motivation:
>
Hi,
I would like to propose splitting the Swift implementation
to its own repository.
Motivation:
* We want to make the Swift implementation Swift Package
Manager compatible.
* It requires a top-level Package.swift.
See also: https://www.swift.org/documentation/package-manager/
Approach
Hi,
Thanks for sharing your thoughts! It seems that we should
try this. I'll start a vote for this.
Thanks,
--
kou
In <20250516.174834.1553983659340140685@clear-code.com>
"[DICSUSS] Split Swift to separated repository" on Fri, 16 May 2025 17:48:34
+0900 (JST),
Sutou Kouhei wrote:
>
Hi,
Good point! I agree with the concerns. But the concerns are
still valid even if we keep swift/ in
apache/arrow... Because the current implementation is
difficult to use by users. (Users can't use Swift Package
Manager to use the Swift implementation.)
Let's see what happens by repository spli
> Is it fair to say most users of Arrow C++ do that via Python/R or shared
libraries? Making the migration to a recent C++ standard relatively safe?
I would say so. For some C++ dependents I know of, they either don't depend
on very recent versions e.g. Velox (C++17) on Arrow 15.0.0 [1], or are
al
I just signed up to be at the conference to attend the summit, so I can
also help with selection if not too late!
On Mon, May 19, 2025 at 8:15 AM Li Jin wrote:
> Sorry for missing this email. I volunteer as well.
>
> (I have been working with / building Arrow-based data processing
> systems sinc
+1
On Mon, May 19, 2025 at 4:03 PM Sutou Kouhei wrote:
> +1
>
> In
> "[DISCUSS][C++] Switch to C++20" on Mon, 19 May 2025 18:14:27 +0200,
> Antoine Pitrou wrote:
>
> >
> > Hello,
> >
> > I am proposing that we switch Arrow C++ to require C++20.
> >
> > C++20 will offer support for more C++
+1
Is it fair to say most users of Arrow C++ do that via Python/R or shared
libraries? Making the migration to a recent C++ standard relatively safe?
--
Felipe
On Mon, May 19, 2025 at 1:14 PM Antoine Pitrou wrote:
>
> Hello,
>
> I am proposing that we switch Arrow C++ to require C++20.
>
> C++
@Andrew: The current proposal in the document is essentially zero-copy
compatible with the Parquet Variant (give or take the differences in
how variable length binary values are represented in Parquet vs Arrow,
and the proposal allows for any of Binary/LargeBinary/BinaryView to
represent the value
+1
In
"[DISCUSS][C++] Switch to C++20" on Mon, 19 May 2025 18:14:27 +0200,
Antoine Pitrou wrote:
>
> Hello,
>
> I am proposing that we switch Arrow C++ to require C++20.
>
> C++20 will offer support for more C++ language and standard library
> features, such as:
>
> - concepts
> - gener
+1. I am supportive of this, though I still have concerns given the
current lack of representation, activity and support for the swift
impl. Just worried about it falling by the wayside.
That aside, thanks for the work on this Kou!
--Matt
On Mon, May 19, 2025 at 1:47 PM Ruoxi Sun wrote:
>
> +1.
+1
Thanks Kou.
On Fri, May 16, 2025 at 1:49 AM Sutou Kouhei wrote:
>
> Hi,
>
> This is a similar discussion to the "[DISCUSS] Split Go
> release process" thread[1], the "[DISCUSS] Split Java
> release process" thread[2], the "[DISCUSS] Split R release
> process" thread[3], the "[DISCUSS] Split C
+1. Thank you kou for driving this!
*Regards,*
*Rossi SUN*
On Mon, May 19, 2025 at 9:17 AM Antoine Pitrou wrote:
>
> +1, I am supportive of this change as well.
>
> Regards
>
> Antoine.
>
>
> Le 16/05/2025 à 10:48, Sutou Kouhei a écrit :
> > Hi,
> >
> > This is a similar discussion to the "[DI
+1
*Regards,*
*Rossi SUN*
On Mon, May 19, 2025 at 9:14 AM Antoine Pitrou wrote:
>
> Hello,
>
> I am proposing that we switch Arrow C++ to require C++20.
>
> C++20 will offer support for more C++ language and standard library
> features, such as:
>
> - concepts
> - generic lambdas with explicit
+1, I am supportive of this change as well.
Regards
Antoine.
Le 16/05/2025 à 10:48, Sutou Kouhei a écrit :
Hi,
This is a similar discussion to the "[DISCUSS] Split Go
release process" thread[1], the "[DISCUSS] Split Java
release process" thread[2], the "[DISCUSS] Split R release
process" t
Hello,
I am proposing that we switch Arrow C++ to require C++20.
C++20 will offer support for more C++ language and standard library
features, such as:
- concepts
- generic lambdas with explicit type parameters
- designated initializers
- calendar and timezone functions (currently, our Wind
Sorry for missing this email. I volunteer as well.
(I have been working with / building Arrow-based data processing
systems since 2017. Perhaps I can provide some perspectives from use
cases in addition to traditional SQL systems, e.g., streaming, time
series, ML, numerical computation etc)
On Su
23 matches
Mail list logo
