We've detected calls to Rf_error in your C++ code, which may be problematic, see RcppCore/Rcpp/issues/1247. Rcpp will warn about these calls in the near future, and will error later on. The purpose is to force package developers to think about their uses of Rf_error to:
- substitute them with
Rcpp::stop in most cases, which does proper unwinding, calling destructors in the process to avoid memory leaks; or
- protect them with parenthesis as in
(Rf_error)(...) if these uses are justified (e.g. in callbacks that are passed on to R functions).
Please review your Rf_error calls and adjust them accordingly.
We've detected calls to
Rf_errorin your C++ code, which may be problematic, see RcppCore/Rcpp/issues/1247. Rcpp will warn about these calls in the near future, and will error later on. The purpose is to force package developers to think about their uses ofRf_errorto:Rcpp::stopin most cases, which does proper unwinding, calling destructors in the process to avoid memory leaks; or(Rf_error)(...)if these uses are justified (e.g. in callbacks that are passed on to R functions).Please review your
Rf_errorcalls and adjust them accordingly.