Cleanup of flycheck/flymake info and warning messages #449
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.
What
Cleanup of flycheck/flymake info and warning messages.
Why
We should keep the code base as clean as possible.
Note
This is a more or less mechanical go through of all info and warnings produce by flycheck and trying to resolve them. (I hope and think that flycheck uses the same backbone functions to check for problems as flymake so this work would cover for a similar exercise using flymake.)
I know you are not a big fan of these huge PRs but it is mostly small changes affecting docstrings. There are a few code changes but should not affect execution.
Common things that are fixed are:
Not all of these are fixed either. Not all functions have been given docstrings. Not all parameters have been added in capital letters.I might have missed something. Anyway -- I have tried fix that but given up due to it either does not make sense to add it or most often, I could not come up with something decent enough so juts left it as is.
There is no Changelog for this work either. If it gets accepted I can add a Changelog item covering the whole initiative.