Change Details

Missing `\n` at the end of `log!` and `log_chronik!` macro invocations in Rust files are now reported by LogLint. Note this currently has known false-negatives: string literals spanning multiple lines in Rust are done like this: ``` let string = "long text that \ doesn't fit in one line"; ``` The current regex doesn't catch this, as in C/C++ the equivalent would be: ``` char *string = "long text that " "doesn't fit into one line"; ``` This will need to be addressed.

Missing `\n` at the end of `log!` and `log_chronik!` macro invocations in Rust files are now reported by LogLint. Since string literals in Rust are allowed to contain newline characters, we need to insert a `\s` into the regex.

Missing `\n` at the end of `log!` and `log_chronik!` macro invocations in Rust files are now reported by LogLint. Note this currently has known false-negatives: string literals spanning multiple lines in Rust are done like this: ``` let string = "long text that \ doesn't fit in one line"; ``` The current regex doesn't catch thiSince string literals in Rust are allowed to contain newline characters, as in C/C++ the equivalent would be: ``` char *string = "long text that " "doesn't fit into one line"; ``` This will need to be addressedwe need to insert a `\s` into the regex.