eellak/build-recorder

`finfo` data structure

Opened this issue · 1 comments

If not for my #144 hashmap implementation (which provided a huge performance improvement, 33% when building wine) ,then what?

Regarding the data structure. It's not worth implementing it now since we eill be making build recorder a multithreaded program. That means that all state must be switched with thread safe state. That is immutable state, state protected by locks and lock/wait free state.

In other words, once #151 is complete, this will be our next goal.