I would also love to see a canonical way to do this! My personal workaround has been to guard my own include with #ifndef ARROW_FLAG_DICTIONARY_ORDERED (but that's clearly a hack).
On Mon, May 9, 2022 at 3:28 PM Tomek Drabas <draba...@gmail.com> wrote: > I am new to this board so please, let me know if any of this doesn't make > sense. > > I am building a FligthSQL example with DuckDB backend. DuckDB already has > an Arrow interface defined in duckdb.h that returns ArrowArray. However, > the import is not guarded in any way, and ArrowArray is redefined in > duckdb.h, so including arrow/c/bridge.h throws an error that ArrowArray is > defined in multiple places. > > I'd like to propose adding canonical guardrails in arrow/c/bridge.h to > avoid this. Is this the best way to do this? > > Thanks, > -Tom >
