Hello everyone! I'm Mossa, I'm one of the maintainers of extendr, an automated generation of bindings project for Rust code, for use in R-packages.
I'm writing to you, as R 4.4.3 was just released, and there have not been follow-up on an issue important to us. Link to the issue as discussed on r-devel https://stat.ethz.ch/pipermail/r-devel/2024-October/083666.html A community member has provided a suggestion to a patch here https://github.com/r-devel/r-svn/pull/182, and we have also attempted to bring it up on Bugzilla: https://bugs.r-project.org/show_bug.cgi?id=18806 TLDR: Default `R CMD check` uses additional CRAN-specific checks for Rust, instead of keeping this behind the --as-cran flag. I would like to say, that there is a growing interest in Rust within the R community. And generally, Rust becoming a widely adopted language within the Python community (including the scientific part of that community). It is time to deal with the pain points with using Rust in R. Therefore, I would kindly ask that we have a dialogue on how to remedy the issue above first, and how we may deal with other issues going forward. There are both challenges embedded in R itself, and the current CRAN policy for Rust is prohibitive. Mossa Merhi Reimert Postdoctoral Researcher K�benhavns Universitet Department of Veterinary and Animal Sciences Animal Welfare and Disease Control Gr�nneg�rdsvej 8 1870 Frederiksberg C Denmark +45 35324135 mo...@sund.ku.dk<mailto:mo...@sund.ku.dk> [[alternative HTML version deleted]]
______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
