This pull request fixes an issue where any line ending with end was triggered, regardless of it being an end statement. Now, a whitespace character and the word end are required.
Additionally, it includes linting improvements and extends rules to apply to type selections as well as switch cases.
Linting requirement have been adjusted to 10.0 instead of 8.0 to avoid regression.
We might want to consider relaxing this if trouble shows up.
There are a few special cases that we might want to adjust:
[x] "missing-spaces-around-seperators" trigger on allocation of type_t::object. We can fix this by not doing this rule if its preceeded by the _t pattern.
[x] Exclamation points ! in printed messages also trigger the space before comments rule.
[x] String formats trigger the missing spaces after comma. Can one safely put a space in the format string or does it change the meaning of the string?
This pull request fixes an issue where any line ending with
endwas triggered, regardless of it being an end statement. Now, a whitespace character and the wordendare required.Additionally, it includes linting improvements and extends rules to apply to type selections as well as switch cases.
Linting requirement have been adjusted to 10.0 instead of 8.0 to avoid regression. We might want to consider relaxing this if trouble shows up.
There are a few special cases that we might want to adjust:
type_t::object. We can fix this by not doing this rule if its preceeded by the_tpattern.!in printed messages also trigger the space before comments rule.