refactor: normalised namespaces, updated file structure and applied stricter warning levels #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomezpl
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to clean up the project in general - starting with namespaces, each module is now part of the global
lepus::namespace, and module namespaces have been converted into more typing-friendly lowercase counterparts:lepus::gfx::lepus::engine::lepus::system::lepus::util::Source files structure and CMakeLists have been updated accordingly.
In addition, CMake has been configured to use higher warning levels, and to treat warnings as errors (only in MSVC, as on the whole that seems to be more lenient than GCC). Going forward warnings will likely be suppressed on a case-by-case basis but it should be enough to prevent some of the more major mistakes.
Minor code changes have been made across the project to comply with the warnings.
Closes #33