CRAN Package Check Results for Package lazyeval

Last updated on 2026-05-13 09:51:49 CEST.

Flavor	Version	Tinstall	Tcheck	Ttotal	Status	Flags
r-devel-linux-x86_64-debian-clang	0.2.3	5.53	42.69	48.22	OK
r-devel-linux-x86_64-debian-gcc	0.2.3	5.83	33.39	39.22	OK
r-devel-linux-x86_64-fedora-clang	0.2.3	8.00	64.33	72.33	OK
r-devel-linux-x86_64-fedora-gcc	0.2.3	9.00	75.01	84.01	OK
r-devel-windows-x86_64	0.2.3	13.00	71.00	84.00	OK
r-patched-linux-x86_64	0.2.3	5.64	38.62	44.26	OK
r-release-linux-x86_64	0.2.3	5.13	39.02	44.15	OK
r-release-macos-arm64	0.2.3	2.00	18.00	20.00	OK
r-release-macos-x86_64	0.2.3	6.00	68.00	74.00	OK
r-release-windows-x86_64	0.2.3	18.00	69.00	87.00	OK
r-oldrel-macos-arm64	0.2.3	2.00	62.00	64.00	NOTE
r-oldrel-macos-x86_64	0.2.3	7.00	87.00	94.00	NOTE
r-oldrel-windows-x86_64	0.2.3	21.00	76.00	97.00	NOTE

Check Details

Version: 0.2.3
Check: compiled code
Result: NOTE File ‘lazyeval/libs/lazyeval.so’: Found non-API calls to R: ‘PRENV’, ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’, ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_PRCODE’, ‘SET_PRENV’, ‘SET_PRVALUE’, ‘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-oldrel-macos-arm64, r-oldrel-macos-x86_64

Version: 0.2.3
Check: compiled code
Result: NOTE File 'lazyeval/libs/x64/lazyeval.dll': Found non-API calls to R: 'PRENV', 'PRVALUE', 'R_PromiseExpr', 'Rf_allocSExp', 'Rf_findVarInFrame3', 'SETLENGTH', 'SET_GROWABLE_BIT', 'SET_PRCODE', 'SET_PRENV', 'SET_PRVALUE', '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-oldrel-windows-x86_64