A question about garble which confused me a lot..

[Ch111p]

It's a great project! I have learnt a lots from these codes about how to obfuscate symbol to a language, especially when it has reflection mechanism.
But now i have little confused about the code. As fat as I know, the data in KnownReflectAPIs is saved to a temp file to each package. When a new package was compiled, it will load the main-cache.gob to get the deps list. According to the list, it will load all temp files to get the KnownReflectAPIs in current. It's so elegant, but here is the question: to make the KnownReflectAPIs be accurate, we should keep the compile order follow to topological order based on dependencies. It's this order guaranteed by official go compiler? And because the compile stage is in parallel, is it possible that the temp file hadn't be created/wrote when trying to read the file? I haven't seen any guarantees(like filelock) in code (Maybe I missed it?)

[mvdan]

You're correct in your assumption: go build guarantees the order of packages being built do that all dependencies of each package come first. Parallelism happens for sure, but never breaking that rule.

[Ch111p]

That's make sense. So one package would be compiled until all it's dependencies be compiled completely. Thanks for your reply😊!