Joakim Hassila
Joakim Hassila
This is actually very nice for more complex schemas
I started on some very basic docs for the reader in #76 but can try to help out with an initial stab on the writer too (would like you to...
What would be next step for this one? Doc in e.g. wiki or what are your thoughts?
Ok, cool - was https://github.com/mzaks/FlatBuffersSwift/pull/78 also done and should I kill that PR, or? What is the issue with the FlatBuffersEnumerationVector (I'm probably missing something obvious)
FWIW, I don't think it would be unreasonable to take a local copy (and free it accordingly) of the Data as this is a usability convenience initialiser - anyone caring...
4. I was probably unclear, I never advocated supporting un unsafe interface - just pointing out that someone having a `Data` object and wanting to avoid a copy from our...
Shouldn't the reader/builder also be using namespaces in the generated code - seeing them as top level in contactList.swift generated code - would cause trouble if having multiple schemas in...
(specifically, the flatbench now uses the contactList builder&reader instead of the framework one... A bit unexpected.)
Ah, I see (not a Swift expert by any means yet). Will ponder if I can think of any better solution for packaging.
Super to see this in progress! Just one quick initial comment/question while browsing, push/pop is documented as `Complexity: O(log n)` - although if skipping levels [as mentioned in article referenced...