Closed famuvie closed 9 months ago
One thought here is that we detect a set of names that we know will cause C++ name conflicts - presumably int
, double
, etc. and check during the C++ code generation phase.
I'm proceeding to insert a check early in modelDef creation in branch fix_1335
.
In addition to checking C++ keywords, Values
and NimArr
cause problems but not various other keywords from nimble's C++ or Eigen. There may be others that are problems.
Dear all,
Similarly to #1219, using
int
as a parameter name (after intercept) leads to a compilation error, which is not straightforward to track back to the source of the problem.Created on 2023-07-27 with reprex v2.0.2
Perhaps some detection of invalid node names with a more informative error message would be useful?
Best. ƒacu.-