We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in accordance with Google C++ styleguide and in order to keep code portability we should avoid unix directory shortcuts. https://google.github.io/styleguide/cppguide.html#Names_and_Order_of_Includes
seems that with the project structure we have we're unable to do that.
should we be worried about that?
The text was updated successfully, but these errors were encountered:
also if we'll use some code quality control tools?
Sorry, something went wrong.
I think that depends on how strict the tools are. Most likely they will allow us to use these kind of paths.
No branches or pull requests
in accordance with Google C++ styleguide and in order to keep code portability we should avoid unix directory shortcuts. https://google.github.io/styleguide/cppguide.html#Names_and_Order_of_Includes
seems that with the project structure we have we're unable to do that.
should we be worried about that?
The text was updated successfully, but these errors were encountered: