parcall: simplify usage print #68
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@maximilianfridrich and me think that the
re_hprintf(pf, "%s", usage);form was only to avoid thegnu-zero-variadic-macro-argumentswarning of clang compiler.For the shorter form
re_hprintf(pf, usage);, I hope that I am right with the assumption that the warning can be suppressed without any risk. Like it is done now with the-Wno-gnu-zero-variadic-macro-argumentsswitch.The warning is still printed in editors that use LSP clangd if
compile_commands.jsonwas generated by gcc. We assume that for this purpose we should switch to clang compiler.@sreimers am I right with these assumptions?