Explicit Rcpp:: in the initalize method for C++ classes wrapped inside modules #980
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Otherwise the Rcpp functions are unknown when objects are initialized, unless Rcpp is attached.
Created on 2019-07-21 by the reprex package (v0.3.0)
Session info
This occurs when modules are created explicitly via
Module()
, both inline (see above) and in packages. The latter case can be seen e.g. usingRcpp.package.skeleton()
and replacingloadModule("yada", TRUE)
withyada <- Module("yada")
and runningnew(yada$World)$greet()
after installing and loading the package.This not an issue for the common case of using
loadModule()
in packages, where typicallyimport(Rcpp)
is in theNAMESPACE
, otherwise we would observe the same behavior.The effectiveness of using
Rcpp::
can be tested by re-running the example above after intalling Rcpp from the branchThe object can now be created even prior to Rcpp being attached.