Looks it really might be. document_order_first() takes 10ms every time it's getting executed: https://github.com/CryZe/livesplit-core/blob/07d3c41b4e06853e64efbfa4c4bb9fc5b12ccfe1/src/parser/livesplit.rs#L98 …
Yeah, that's what I just realized. Since you are expecting a single node, it definitely doesn't matter what order the nodes are in
-
-
Maybe add a note in the documentation that it's faster to use .iter() if document order is not needed.
-
Not a bad idea. I do still want to cache the computation of the ordering though.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.