paleolimbot commented on PR #431: URL: https://github.com/apache/arrow-nanoarrow/pull/431#issuecomment-2061169372
> Do we want to go the route of a registry and having users define their own? Great point! I'm still feeling my way through how users should interact with this. The part where the concept of a registry is difficult to avoid (global or tightly scoped) is when doing conversion to/from Python objects with nested type support. Without a registry, how would one produce/consume a `struct<geoarrow.polygon, uuid>` without inefficiently bouncing through deeply-nested Python output or without every package that does consuming explicitly opting in to every possible extension type? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
