Conversation
e544706 to
354298d
Compare
DavisVaughan
approved these changes
Mar 5, 2026
DavisVaughan
reviewed
Mar 5, 2026
354298d to
d719674
Compare
e0bfc6a to
78cb979
Compare
d719674 to
36b043a
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Branched from #1076
R core just removed access to a bunch of APIs, just in time to put our new r-devel build (#1076) to good use.
The main change is that we no longer unlock our private namespaces and environments. Instead we wait until they are fully initialised to lock them. In debug builds we never lock them to allow hot-reloading when a .R file changes.
Otherwise we follow what we've been doing in rlang, lobstr, vctrs, and other packages regarding compatibility with C API. E.g. in
zap_srcref()orobj_size(). We use new APIs (with polyfills for old R compats) or new workaround approaches.I've also proactively removed usage of
ATTRIB()andSET_ATTRIB()as well (except in the altrep utils) since these have been promoted from NOTE to WARNING on CRAN.