Fix asserts in Value::setComment #1445
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.
The existing asserts seem to not be what was intended; they appear to have been mistranslated in pull/877.
The first assert for
comment.empty()
was previously a check that a providedconst char*
parameter was not null. The function this replaced accepted empty strings, and the if() statement at the start of this function handles them.The second assert for
comment[0] == '\0'
was written whencomment
was aconst char*
, and was testing for empty c-string input. This PR replaces it withcomment.empty()
to match the original intent.