Merged
Conversation
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.
Closes #6140; follow-up to #6074
Looking more carefully,
coerceAs()will receive a factor as-is from R unless it's doing some lazy evaluation. It's only job is to map what its input into the factor structure it receives.So I don't think
coerceAs()is doing anything wrong, rather, the test is poorly structured:i.e. in the second case, 'x' will always come first regardless of which level it is, while in the first, the first level always comes first.
Therefore I think the proposed edit (to always supply levels explicitly) is appropriate -- it abstracts the base-owned logic of generating levels away.
An uglier alternative is to use
coerceAs(order(c('x', 'y')), factor(c('x', 'y'))). I don't see any real advantage of this approach.