James Courtney

> > > I can serialized the object back into the same byte[] to avoid allocating a new byte[]. > > > > > > Are you using FlatSharp for...

> I don't think I would use an object pool in my case. I would look for a completely stack based solution. If I'm force to allocate then I'd prefer...

> I'd like to be able to extract (visit, view) or get a Span or Memory to a specific entry in the buffer to pick out some value. > I...

@pattymack and @joncham -- I have a prototype of object pooling if you'd like to provide some feedback. The nuget packages are attached here: [FlatSharp.Runtime.7.0.0.zip](https://github.com/jamescourtney/FlatSharp/files/10008321/FlatSharp.Runtime.7.0.0.zip) [FlatSharp.Compiler.7.0.0.zip](https://github.com/jamescourtney/FlatSharp/files/10008322/FlatSharp.Compiler.7.0.0.zip) There are a few...

Version 7.0.0 is published with experimental support for object pools. Feedback welcome. https://github.com/jamescourtney/FlatSharp/wiki/Object-Pooling

Thanks for this -- I am interested. Please turn this into a full PR. I am planning a release of version 7.5 soonish with a few things I haven't finished...

Thanks for the contribution! Give me a couple of days to mull this over; FlatSharp's unions used to support behavior similar to this. The reason that I moved away from...

Did you ever get results of the benchmark? Another way to do this would be to have a `DelegateVisitor` implementation that is easy to construct.

I've looked a little bit at this using LinqPad, and the delegate implementation looks substantially worse in terms of number of bytes emitted by the JITer. You can find a...

Agree -- You'll want to do a pull from my main branch since I've made some changes to exception handling. You should be able to emulate what I do in...