CRAN Package Check Results for Package lazyeval

Last updated on 2026-06-18 01:52:50 CEST.

Flavor	Version	Tinstall	Tcheck	Ttotal	Status	Flags
r-devel-linux-x86_64-debian-clang	0.2.3	6.17	42.55	48.72	OK
r-devel-linux-x86_64-debian-gcc	0.2.3	4.84	33.16	38.00	OK
r-devel-linux-x86_64-fedora-clang	0.2.3	7.00	63.93	70.93	OK
r-devel-linux-x86_64-fedora-gcc	0.2.3	9.00	111.21	120.21	OK
r-devel-windows-x86_64	0.2.3	27.00	71.00	98.00	OK
r-patched-linux-x86_64	0.2.3	6.12	39.17	45.29	OK
r-release-linux-x86_64	0.2.3	6.16	39.31	45.47	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	17.00	68.00	85.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	20.00	81.00	101.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