Hi,
I would like to thank Fernando for raising this concern here: I also think
that we still do not put enough effort in the documentation :) I admit that
when I started in the project, I also had that need and just had some time
to go through the code.
First, I find it useful to distinguish type
I understand the concern, especially with the project changing that
quickly. However, I haven't found a good material that I can use to learn
how to use the crate. I know that each module has a lot of tests (which I'm
thankful for) but going from one test case to the other doesn't work well
as lear
>
> We should be careful with the balance of content between the Restructured
> Text Format documentation and the documentation in the crate that gets
> published to docs.rs though. The rustdoc documentation is unit-tested to
> ensure that it is always up to date and we will have to manually update
I think that it would be great to produce this kind of content. I'm giving
a presentation on Arrow to my local Rust meetup (virtually) next week and
these are similar to the topics I will be covering there.
We should be careful with the balance of content between the Restructured
Text Format docum
Java and C++ have tutorials in Restructured Text Format in the docs folder
[1]. I think creating something similar for Rust might be the best place
to start. These are rendered on the website. For example Java is located
at [2].
[1] https://github.com/apache/arrow/tree/master/docs/source
[2] h
I was working on the blog post I mentioned before regarding Arrow usage
(rust) and how to use the different elements available in the create. After
some thought, these were the topics I want to include:
1. Arrays examples and how they look like
Basic arrays and nested arrays
The buffer st
I've fixed the thing and added PR https://github.com/apache/arrow/pull/8461
May I ask someone for a review? I suggest Philip Moritz who contributed the
original cython integration layer would be a good candidate.
Since I cannot assign reviewers, I thought maybe it is a good idea to write
in the mai
+1 (binding)
Verified source, binary and wheel artifacts on macOS Catalina.
Also executed the automatized crossbow verification tasks [1].
[1]: https://github.com/apache/arrow/pull/8479#issuecomment-709965167
On Fri, Oct 16, 2020 at 4:30 AM Sutou Kouhei wrote:
>
> > * Python 3.8 wheel's test
