>
> In terms of what to support, I would personally recommend waiting for
> someone who wants to use Rust / arrow on a specific platform (and thus has
> the time to help us test). Without user input I don't have any sense of
> which platforms you list below are the most important
I want to use it
I agree with Andrew. If we are going be serious about supporting
additional architectures we should merge these changes along with
changes adding them to CI.
On November 12, 2020, Andrew Lamb wrote:
> In general I think expanding support for additional architectures is a
> good
> idea. The list
In general I think expanding support for additional architectures is a good
idea. The list of possible features and support you describe is pretty
substantial, and I suggest we are careful about taking on too much too soon.
In terms of what to support, I would personally recommend waiting for
some
In addition to the previous e-mail there are some changes at companies like
Apple:
Next-generation will ship will Aarch64 as you know. Since my local test
showed that we can build on:
* aarch64-unknown-linux-gnu
But we need sysroot image for:
* aarch64-apple-darwin
Aarch64 on apple is another topi
Hi Team;
There are 3 topics fall under this:
* no_std compatibility
* endianness compatibility
* target datapath size (32-bit/64-bit, rust naming target_pointer_width)
So after the sync call yesterday, Micah said that there were efforts on
that for some time at Java, C++ side. That's nice. Curren
