GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
A typical build on a modern version of Mono/.Net results in roughly 160 warnings. We should review these warnings and either fix them or silence them when harmless (e.g. unused private field warning for reserved fields in interop structures.)
(Originally accidentally posted in a pull request related to this) In addition to normal warnings I would like to ask if going over the code and look at warnings given from utilities like ReSharper could be included in this. Perhaps including warnings on code style standards?
Static analysis is really useful, but it takes some effort to distinguish useful warnings from fluff. When I last tried this on OpenTK, I got several thousands of warnings but only a few dozen of those were actual code quality issues.
For example, in the attached screenshot it is suggested to move Lindgren.Network/Encryption to Lindgren/Network/Encryption and rename private variables from m_* to _*. These are cosmetic issues. Fixing these would make other forks more difficult to merge and potentially introduce new bugs, for a very modest improvement in code quality.
I would happily accept PRs that fix potential issues revealed through static analysis, but I am quite skeptical about the value of fixing cosmetic issues in private code.
Add XML documentation to matrix Add methods.
Fixes warnings [#61] about missing documentation on public members.
Remove unused field.
Fixes warnings [#61] by removing an unused field.
Remove unused fields/variables.
Fixes warnings [#61] by removing some unused variables and an unused field.
Field was private so no inheritance concerns.
Add #pragma warning disable for unused field warnings.
Fixes warnings [#61] by disabling unused field warnings for two structures in
HidProtocol. These fields aren't currently used by OpenTK but the stuctures are
used in native marshalling so must match the documented structures perfectly.
Merge pull request #190 from Frassle/warnings
[Issue #61] Fix warnings.
@varon @daerogami There is practically nothing left of this issue, and it should probably be closed. Smaller, more quantifiable issues can be opened for any warnings still present.