NEWS.md
Trigger run (#14).
ci: Trigger run
ci: Latest changes
Use pkgdown branch (#13).
ci: Use pkgdown branch
ci: Updates from duckdb
ci: Trigger run
Install via R CMD INSTALL ., not pak (#12).
ci: Install via R CMD INSTALL ., not pak
ci: Bump version of upload-artifact action
Auto-update from GitHub Actions.
Run: https://github.com/krlmlr/bindrcpp/actions/runs/10425482950
Auto-update from GitHub Actions.
Run: https://github.com/krlmlr/bindrcpp/actions/runs/10200119080
Auto-update from GitHub Actions.
Run: https://github.com/krlmlr/bindrcpp/actions/runs/9727973898
Auto-update from GitHub Actions.
Run: https://github.com/krlmlr/bindrcpp/actions/runs/9691614338
xxx_env_yyy_wrapped()
functions expect a list as payload, and a callback function with List
instead of PAYLOAD
as second argument. This helps controlling the lifetime of objects associated with a callback: these can be placed in an XPtr
inside the List
. The xxx_env_yyy()
functions have been aliased to xxx_env_yyy_typed()
(#7).Initial CRAN release.
create_env_string()
creates an environment with active bindings, with names given as a character vector. Access of these bindings triggers a call to a C++ function with a fixed signature (GETTER_FUNC_STRING
); this call contains the name of the binding (as character) and an arbitrary payload (PAYLOAD
, essentially a wrapped void*
).create_env_symbol()
is similar, the callback function accepts the name of the binding as symbol instead of character (GETTER_FUNC_SYMBOL
).populate_env_string()
and populate_env_symbol()
populate an existing environment instead of creating a new one.LinkingTo: bindrcpp
and #include <bindrcpp.h>
to access these functions from your package.bindr
: create_env()
and populate_env()
.