You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the idea is you're just commenting out the #include to test levelization, but not necessarily removing it permanently? Because if you're removing it, you should just delete it. It'll still exist in git history.
So the idea is you're just commenting out the #include to test levelization, but not necessarily removing it permanently? Because if you're removing it, you should just delete it. It'll still exist in git history.
Yes, if I was removing it, it would not be a problem.
What caught me: I was investigating newly discovered circular dependency and wasn't sure what caused it. So I was commenting out newly added headers, trying to find the point where dependency was introduced and was running in circles because the script ignored the commented-out code.
Issue Description
The levelization.sh script counts as included files that are commented out. I.e.
This is not very obvious and creates confusion for someone who is trying to investigate and resolve issues with dependencies.
The proposal: as a minimum, add simple checks for a single line comment
//
.The text was updated successfully, but these errors were encountered: