Async version needed

[mycroftjr]

For huge .unity scene files, the parser is prohibitively slow to even load the document. I ended up rolling my own file scanner using mmap instead.

My use case was scanning values for certain strings, finding the relevant GameObject, and then following the Transform parent chain to get the positions and the names of all the associated GameObjects for more context on where the item is. (I'd have liked the absolute world position for the original GameObject, but with rotations in the mix that's more quaternion math than I wanted to deal with.)
(Pro-tip: at least for my scenes, the fileIDs in the headers can be binary searched, since after the first 3 Settings objects, the entries are defined in order of fileID.)

[sp-ricard-valverde]

Hey @mycroftjr !

Thanks for the suggestion, using mmap was a clever approach 👍 .
Sadly I can't invest the time to improve the parser. It's open to contributions though, but for this particular improvement I would say that unity-yaml-parser is based on PyYAML to scan the document and the kind of improvement(I think) you are suggesting might need rewriting our own yaml parser from scratch.