Warn or error if Rcpp.h (and R.h) was included

未關閉
#142 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
45/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
cpp, r
領域
tooling

研究方向

Start in RcppEigen.h and inspect how the Rcpp and R header guards are detected before Eigen is included. Trace the include order described in the issue, then confirm that including R.h or Rcpp.h before RcppEigen.h produces the intended warning without changing the normal direct-include path.

由索引模型根據 Issue 內容生成。

描述

As discussed over in Rcpp in https://github.com/RcppCore/Rcpp/pull/1402 we are seeing some side effects from some package including R.h and later including possible also Rcpp.h and then RcppEigen.h leaving some of the masking of R's own error() function as Rf_error() to not be effective so that it later clashes with Eigen function error().

In general, it is always cleanest to just include RcppEigen.h as it does take care of both the others. For RcppArmadillo this once lead to issues to that it (very early on) switch to an actual compile error. We may do that one day but for now it might be a good idea to at least warn from RcppEigen.h if the header guards for either or both of Rcpp and R are seen.

主要語言
C++
星號
118
分支
43
PR 合併指標
30 天內沒有已合併 PR

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

RcppCore/RcppEigen 的其他 Issue

查看 RcppCore/RcppEigen 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。