Michael Eisel

looking closer, i guess it's not arm64_32, the target says `arm64-apple-watchos7.0-simulator`. why would the simulator use arm64? is this a new arm mac? my watchos knowledge is limited

i thought watchos only used arm64_32 and armv7k, does it also now use arm64?

is this still a problem on latest master?

That'd be great, thanks!

To be clear, a well-written binary decoder/encoder would be faster, but I don't know if one exists right now (e.g. a fast MessagePack encoder/decoder)

To elaborate, the string length would stay where it already was in the document, just the string itself would be moved

It's hard to write out completely using that syntax, but every str would move the `data` piece to the end of the document, right after the previous string's `data`. So...

yes, that's true, it would depend on how the data is provided to the parser

i don't have a particular one at the moment for this, just thought i'd throw it out to brainstorm

I thought `atos` used the offset into the binary, not the offset into the text segment, is that not true? And if it is, would we need to calculate the...