Skip to content
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

[R] Don't re-export S3 methods from bit64 #45399

Open
MichaelChirico opened this issue Jan 31, 2025 · 2 comments
Open

[R] Don't re-export S3 methods from bit64 #45399

MichaelChirico opened this issue Jan 31, 2025 · 2 comments

Comments

@MichaelChirico
Copy link
Contributor

#' @importFrom bit64 print.integer64
bit64::print.integer64
#' @importFrom bit64 str.integer64
bit64::str.integer64

These methods are slated to be removed from {bit64}'s NAMESPACE. Is there a particular reason to re-export them like this?

FWIW, I don't see any other call sites for these functions on GitHub.

See r-lib/bit64#76.

@amoeba amoeba changed the title Don't re-export S3 methods from bit64 [R] Don't re-export S3 methods from bit64 Jan 31, 2025
@amoeba
Copy link
Member

amoeba commented Jan 31, 2025

Thanks for the heads up. It looks like they were introduced in #19954 to handle a special case. Do you have a timeline for releasing a new version without the exports to CRAN?

@amoeba amoeba added this to the 20.0.0 milestone Jan 31, 2025
@MichaelChirico
Copy link
Contributor Author

No, but I don't plan on releasing more frequently than 6 months cadence, and it's at least 3 releases before becoming an error, so at a minimum 18 months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants