The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

hellorust: Minimal Examples of Using Rust Code in R

Template R package with minimal setup to use Rust code in R without hacks or frameworks. Includes basic examples of importing cargo dependencies, spawning threads and passing numbers or strings from Rust to R. Cargo crates are automatically 'vendored' in the R source package to support offline installation. The GitHub repository for this package has more details and also explains how to set up CI. This project was first presented at 'Erum2018' to showcase R-Rust integration <https://jeroen.github.io/erum2018/>; for a real world use-case, see the 'gifski' package on 'CRAN'.

Version: 1.2.2
Published: 2024-09-22
DOI: 10.32614/CRAN.package.hellorust
Author: Jeroen Ooms ORCID iD [aut, cre], Authors of the dependency Rust crates [aut] (see AUTHORS file)
hellorust author details
Maintainer: Jeroen Ooms <jeroenooms at gmail.com>
BugReports: https://github.com/r-rust/hellorust/issues
License: MIT + file LICENSE
URL: https://github.com/r-rust/hellorust
NeedsCompilation: yes
SystemRequirements: Cargo (Rust's package manager), rustc
Materials: NEWS
CRAN checks: hellorust results

Documentation:

Reference manual: hellorust.pdf

Downloads:

Package source: hellorust_1.2.2.tar.gz
Windows binaries: r-devel: hellorust_1.2.2.zip, r-release: hellorust_1.2.2.zip, r-oldrel: hellorust_1.2.2.zip
macOS binaries: r-release (arm64): hellorust_1.2.2.tgz, r-oldrel (arm64): hellorust_1.2.2.tgz, r-release (x86_64): hellorust_1.2.2.tgz, r-oldrel (x86_64): hellorust_1.2.2.tgz
Old sources: hellorust archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=hellorust to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.