Flint thinks the filename in an #include is code...

[d-frey]

I use paths that include c++, example:

#include <foo/c++14/bar.hpp>

When I check the file with flint++, I get:

Use prefix notation '++c'.

Postfix iterators inject a copy operation, almost doubling the workload.

For some reason, I have doubt that this will improve my code :)

[JossWhittle]

Good catch, this shows there is a bug in the Tokenizer as an include path should be a string literal. Cheers for the catch, I've hotfixed the Postfix Iterator test to make it avoid false positives and I'll look into the Tokenizer bug asap. :)