Fix R-devel check failures after R_typeToChar relocation and deprecation. - #61
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
1 participant
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.
This PR resolves the CRAN check failures traced to the relocation of
R_typeToCharfromRinternals.htoDefn.hin r89057. The symbol was later marked non-API here.quickr previously used
R_typeToCharto preserve the distinction between S4 objects and plain “object” in error messages. Because the symbol is no longer available through public headers, this patch switches to the publicRf_type2char(TYPEOF(x)). This restores compatibility with current R-devel and clears the CRAN check failures, at the cost of losing the S4/plain-object nuance.This is the minimal, CRAN-safe fix required ahead of the 2025-12-19 retention deadline.