Accept C files ending in a backslash-newline #187
Merged
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.
Related issues
Proposed changes
\
, inspired by a header found in a Llama.cpp test.\
).Enabling "relaxed" parsing mode would also have allowed the failing test to pass, but permitting any invalid code to proceed to future preprocessing phases seems like it would lead to errors that were almost impossible to debug. By providing an allowlist of permitted relaxed cases instead, we can generate a specific warning for each case and introduce additional relaxations over time.
I'll acknowledge that the way I've added a workaround for this specific case is a bit of a hack. A solution that detected
\
at the end of a file and generated afilename:line:col:
style warning immediately would be much better, butfile_source
isn't set up to track tokens that way.Note that while removing the
relaxed
parameter is a breaking change to these interfaces, directly calling the internals of thecodebasin
package was deprecated in 1.2.0, so I don't think it's an issue.