Replies: 1 comment
-
I haven't done anything like that yet. I agree that having some guidelines on understanding the information exposed by the compiler and actions to take depending on what Compile Score reports is a really good idea. I will try gathering data and examples and start a wiki page for this. Thanks for the suggestion. Answering your question:
In my experience most large codebases suffer from massive badly done includes. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I didn't find a doc that explain what are exactly the frontend/backend steps... More generally, it would be great to have some tips about how to interpret the results, what you should look after when you have a long compilation time... is there such a doc somewhere ?
Beta Was this translation helpful? Give feedback.
All reactions