Fix error messages from io:format
and related functions
#8611
+93
−70
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.
Fixes #8568.
This PR introduces a new function
erl_lint:check_format_string/2
, where the second argument can be used to decide if the check should be strict (true
, the default) or relaxed (false
).Strict checking, which is the same as in the current implementation, will check and complain about repeated (eg
~ttp
), conflicting (eg~kKp
) or non-applicable (eg~kb
) modifiers in formatting sequences. Those do not cause errors, though, so while it is ok for linting to check and warn about them, it will cause wrong error messages.Relaxed checking omits the above checks and only reports erroneous format sequences (eg
~q
). Relaxed checking is used byerl_stdlib_errors
to print out error reasons.