CRAN Package Check Results for Maintainer ‘Duncan Garmonsway <nacnudus at gmail.com>’

Last updated on 2024-12-22 13:49:17 CET.

Package NOTE OK
meltr 5 8
nzpullover 13
tidyxl 4 9
unpivotr 13

Package meltr

Current CRAN status: NOTE: 5, OK: 8

Additional issues

rchk

Version: 1.0.2
Check: Rd cross-references
Result: NOTE Found the following Rd file(s) with Rd \link{} targets missing package anchors: melt_delim.Rd: tibble melt_delim_chunked.Rd: tibble melt_fwf.Rd: tibble melt_table.Rd: tibble Please provide package anchors for all Rd \link{} targets not in the package itself and the base packages. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64

Version: 1.0.2
Check: compiled code
Result: NOTE File ‘meltr/libs/meltr.so’: Found non-API calls to R: ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 1.0.2
Check: compiled code
Result: NOTE File 'meltr/libs/x64/meltr.dll': Found non-API calls to R: 'SETLENGTH', 'SET_GROWABLE_BIT', 'SET_TRUELENGTH' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Package nzpullover

Current CRAN status: OK: 13

Package tidyxl

Current CRAN status: NOTE: 4, OK: 9

Version: 1.0.10
Check: installed package size
Result: NOTE installed size is 9.6Mb sub-directories of 1Mb or more: libs 8.6Mb Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Package unpivotr

Current CRAN status: OK: 13

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.