has_name now always returns a single logical value #60
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.
Per discussion in #59 . In #46 I made
has_name()throw an error if you tried to check multiple names in one call, e.g.Four packages on CRAN have code (covered by tests) that uses
has_name()with multiple names, and all of them do this:Instead of breaking their code, I think the spirit of #46 (all assertions return exactly one
TRUE/FALSE) can still be accomplished by using anall()insidehas_name()! That is what I've proposed in this PR.