cran

R packages developed using extendr are not immediately ready to
be published to CRAN. The extendr package template ensures that
CRAN publication is (farily) painless.

Provides functions to compile and load Rust code from R, similar
to how 'Rcpp' or 'cpp11' allow easy interfacing with C++ code. Also provides
helper functions to create R packages that use Rust code. Under the hood,
the Rust crate 'extendr' is used to do all the heavy lifting.

Ilia Kosenkov

rextendr

Call Rust Code from R using the 'extendr' Crate

Claus O. Wilke

Andy Thomason

Mossa M. Reimert

Malcolm Barrett

Josiah Parry

Kenneth Vernon

Alberson Miranda

cran function

In order to publish a Rust based package on CRAN it must meet certain
requirements. These are:<ul>
<li>Rust dependencies are vendored</li>
<li>The package is compiled offline</li>
<li>the <code>DESCRIPTION</code> file's <code>SystemRequirements</code> field contains <code>Cargo (Rust's package manager), rustc</code></li>
</ul>The extendr templates handle all of this except vendoring dependencies.
This must be done prior to publication using <code>vendor_pkgs()</code>.
In addition, it is important to make sure that CRAN maintainers
are aware that the package they are checking contains Rust code.
Depending on which and how many crates are used as a dependencies
the <code>vendor.tar.xz</code> will be larger than a few megabytes. If a
built package is larger than 5mbs CRAN may reject the submission.
To prevent rejection make a note in your <code>cran-comments.md</code> file
(create one using <code><a href="https://usethis.r-lib.org/reference/use_cran_comments.html">usethis::use_cran_comments()</a></code>) along the lines of
"The package tarball is 6mb because Rust dependencies are vendored within src/rust/vendor.tar.xz which is 5.9mb."

CRAN requirements

CRAN compliant extendr packages — cran

In order to publish a Rust based package on CRAN it must meet certain
requirements. These are:<ul>
<li>Rust dependencies are vendored</li>
<li>The package is compiled offline</li>
<li>the <code>DESCRIPTION</code> file's <code>SystemRequirements</code> field contains <code>Cargo (Rust's package manager), rustc</code></li>
</ul>

The extendr templates handle all of this except vendoring dependencies.
This must be done prior to publication using <code>vendor_pkgs()</code>.
In addition, it is important to make sure that CRAN maintainers
are aware that the package they are checking contains Rust code.
Depending on which and how many crates are used as a dependencies
the <code>vendor.tar.xz</code> will be larger than a few megabytes. If a
built package is larger than 5mbs CRAN may reject the submission.
To prevent rejection make a note in your <code>cran-comments.md</code> file
(create one using <code><a href='https://usethis.r-lib.org/reference/use_cran_comments.html'>usethis::use_cran_comments()</a></code>) along the lines of
"The package tarball is 6mb because Rust dependencies are vendored within src/rust/vendor.tar.xz which is 5.9mb."

cran: CRAN compliant extendr packages

Description

Arguments

CRAN requirements