platform for in-memory data. zero-copy streaming messaging and interprocess communication. Languages currently supported include C, C++, C#, Go, Java, JavaScript, MATLAB, Python, R, Ruby, and Rust.
advantages of Arrow (to date). 3. Go allows us to improve the implementation. Implement spec in pure Go Cons: 1. Hard to follow up the changes. 2. Harder to maintain. 3. Hard to insert improvements back to the C++.
project enjoys all the C++ main branch improvements. 2. Any addition that we create using the Go project we can export back to Python/C++ project. Cons: 1. It's much harder ...
headers are required, this means that the dev env’ is more complex than a Go project. Solution is a Dockerfile that has Native C++ and Python bindings for E2E tests.
Where is the best place to log and handle them? For now - every call returns this result_t typedef struct { const char *err; void *ptr; int64_t i; } result_t
linked to a specific Arrow version in a specific OS (Linux AMD64 for example). Do we precompile for each OS? Add to Readme what packages need to be installed alongside?