Comply with expected header for generated Go code #52
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.
Hello! I'm using c-for-go for several projects, and thus far have had to add workarounds to avoid linting code generated by this tool. I just realized that the header generated by the tool doesn't quite comply with the recognized format for generated Go code, as defined in this issue: golang/go#13560.
This resolves that problem and allows linting tools to recognize and skip code generated by this tool.
Before:
After: