-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Un-export S3 methods #76
Comments
Not seen on GitHub:
Definitely used elsewhere:
Searches: |
Confirmed that none of the "2nd generation" of names to be un-exported ( |
All GitHub/CRAN users of exported S3 methods slated for deprecation beginning in the next release have now been notified. That's all I'll do during this release, pending feedback from downstreams on the plan. |
bit64/R/bit64-package.R
Lines 903 to 947 in b6ab4c0
My understanding is these would have been written/exported before the concept of "namespace" was really a thing in R, and before the Imports/Depends separation existed.
These objects were exported as of the initial CRAN release 13 years ago:
cran/bit64@f7e0fac
Probably, they can be un-exported without incident; a glance at a few shows no reference to calling them directly on GitHub.
That said, this will constitute a breaking change in some cases, and should thus be taken up gently, starting with an announcement in the next release and gradual deprecation thereafter.
The text was updated successfully, but these errors were encountered: