The 'R' language includes a set of defined types, but the language itself is "absurdly dynamic" (Turcotte & Vitek (2019) <doi:10.1145/3340670.3342426>), and lacks any way to specify which types are expected by any expression. The 'typetracer' package enables code to be traced to extract detailed information on the properties of parameters passed to 'R' functions. 'typetracer' can trace individual functions or entire packages.
| Version: | 0.2.3 |
| Imports: | brio,checkmate, methods,rlang,tibble,withr |
| Suggests: | knitr,rematch,rmarkdown,testthat (≥ 3.0.0) |
| Published: | 2025-12-03 |
| DOI: | 10.32614/CRAN.package.typetracer |
| Author: | Mark Padgham [aut, cre], Filip Krikava [ctb] (Author of original 'injectr' code on which this package builds; https://github.com/PRL-PRG/injectr), covr authors [cph] (Original authors of sections of code from 'covr' package included here in modified form.) |
| Maintainer: | Mark Padgham <mark.padgham at email.com> |
| BugReports: | https://github.com/mpadge/typetracer/issues |
| License: | MIT + fileLICENSE |
| URL: | https://github.com/mpadge/typetracer,https://mpadge.github.io/typetracer/ |
| NeedsCompilation: | yes |
| Language: | en-GB |
| Materials: | README,NEWS |
| CRAN checks: | typetracer results |