Hey Wes, The StringView/ByteView structure presents some complications with Go in memory handling (particularly with the C ABI) so I added a comment on the RFC outlining this.
TL;DR: Garbage Collection makes it difficult to handle because it's not maintaining a properly typed pointer. I'm gonna keep thinking about this to see if i can come up with a good solution, but I encourage anyone to have a look at my comment on the RFC[1] and add any comments / questions they might have. Thanks! --Matt [1] https://docs.google.com/document/d/1kocVHzEpd-veq2AsoHcsrlaDpezUNOKk2PRzggwAs9w/edit?disco=AAAAdZJ6GHs On Sun, Jul 31, 2022 at 10:05 AM Antoine Pitrou <anto...@python.org> wrote: > > Hi Wes, > > Le 31/07/2022 à 00:02, Wes McKinney a écrit : > > > > I understand there are still some aspects of this project that cause > > some squeamishness (like having arbitrary memory addresses embedded > > within array values whose lifetime a C ABI consumer may not know about > > -- we already export memory addresses in the C ABI but fewer of them > > because they are only the buffers at the array level). We discussed > > some alternative approaches that address some of these questions, but > > each come with associated trade-offs. > > Are any of these trade-offs blocking? > >
