Refactor TYPEOF to enum-style
#224
Merged
Conversation
This file contains 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
|
Shouldn't this be |
I never know. I can make it so 😂 |
Done! Feel free to review this PR, as that would be very good for me 😆 |
Ilia-Kosenkov
approved these changes
Apr 22, 2024
|
I think this is a breaking change. Do you have any plan to reflect the necessary changes to extendr? |
|
Yes! And I'm going to do it very soon. |
|
Great. |
Closed
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.
Replacing #210, #211 and #207. The git churn was getting out of hand.
This PR unifies
TYPEOFoutput to aSEXTYPE, where now,SEXPTYPEis anenum.Furthermore
test.yml's download-action (download-artifact) to use latest version