Closes #1655 add back-compatibility to expr_label()
for incoming is.atomic(NULL)
change in R version 4.4
#1656
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.
Closes #1655
Copy of issue below:
One of the main "significant user-visible changes" for the upcoming R release, v4.4, is that:
is.atomic(NULL)
now returnsFALSE
, asNULL
is not an atomic vector. Strict back compatibility would replaceis.atomic(foo)
by(is.null(foo) || is.atomic(foo))
but should happen sparingly only.expr_label(NULL)
under R <4.4 would return "NULL"expr_label(NULL)
under R 4.4 would return "`NULL`"Although
expr_label()
is already under lifecycle label questioning, this may have minor unintended consequences