Matthew Hambley
Matthew Hambley
As it stands it's not clear that our system testing is giving us much. It's mostly just testing the command line interface as it duplicates the unit tests as far...
Currently rules tend to carry their own exceptions. This makes a certain amount of sense but there are problems when exceptions get complicated. For instance, if you wanted to enforce...
It would be good to get a type hint on the return of `SourceTree.get_tree()` but each implementation will return a different type. For instance Fortran will return an fParser `Program`...
At the moment the abstract `Rule` class does not specify the type of the `subject` argument to the `examine` method. This is due to the fact that it could be...
At the moment each (tree) rule is passed the parse tree which it then pokes about in for its own purposes. The concern is that this may become a performance...
Make sure that everything listed in the "only" list of a "use" statement is, in fact, used. Obviously this can only work where there is an "only" list.
For expediency the Fortran preprocessor strips out all directives. This allows us to ignore #ifdef thereby checking the style of the whole file. Unfortunately it also tears out #include and...
For expediency the C preprocessor strips out all directives. This allows us to ignore `#ifdef` thereby checking the style of the whole file. Unfortunately it also tears out `#include` and...
Some style rules require additional information which only the developer could know. However many have an obvious default or otherwise implied modification associated with them. For instance, when checking that...
The `MissingImplicit` rule checks for the absence of an `implicit` statement and is mollified by finding one. It might be desirable to provide an option to require a specific implication....