I can see how that might be a bit circular. Let me start from the perspective of requirements. We want to be able to reuse the arrow's types and schema, without having to write additional code to move back and forth between compute IR and not-compute-IR. I think that leaves only flatbuffers as an option.
On Wed, Aug 11, 2021 at 3:52 PM Phillip Cloud <cpcl...@gmail.com> wrote: > On Wed, Aug 11, 2021 at 3:51 PM Antoine Pitrou <anto...@python.org> wrote: > >> >> >> Le 11/08/2021 à 21:39, Phillip Cloud a écrit : >> > The benefit is that IR components don't interact much with >> `flatbuffers` or >> > `flatc` directly. >> > >> [...] >> > >> > One counter-proposal might be to just put the compute IR IDL in a >> separate >> > repo, >> > but that isn't tenable because the compute IR needs arrow's type >> information >> > contained in `Schema.fbs`. >> >> This argument seems predated on the hypothesis that the compute IR will >> use Flatbuffers. Is it set in stone? >> > > It's not set in stone, but so far it's the leading contender due to the > need to share elements of Schema.fbs. > > >> >> Regards >> >> Antoine. >> >
