Make is_syntactic_literal() more strict - #1824
Merged
Merged
Conversation
Add an `attributes()` check to `is_syntactic_literal()` to ensure that syntactic-literal-like objects such as factors and arrays are not treated as syntactic literals. Fixes r-lib#1817.
Contributor
Author
|
#1799 is really close to this. Would you like me to fix that in this same PR, or keep it separate? It will make it make sense to split Edit: Technically |
Member
|
A second PR for the other fix would be great, thanks! |
This file contains hidden or 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.
Add an
attributes()check tois_syntactic_literal()to ensure that syntactic-literal-like objects such as factors and arrays are not treated as syntactic literals.Fixes #1817.