[3] is generated when template_var in [1] is visited, but the binding shouldn't be generated because the template variable is not specialized.
[4] and [5] are generated when specialized_var in [2] is visited. [4] is okay because specialized_var is just a global variable being assigned with a specialized template variable (i.e., template_var<int>). However, [5] should be either not generated or be m.attr("template_var_int") = chimera_test::template_var<int>, which I'm not sure which one would be the right way. If we need to generate [5], note that the variable name should be mangled name (e.g., template_var_int) unless specified by config (also, we don't have a way to specify properties for variables).
298 changes Chimera to skip generating [3] and [5].
Generated binding for this source:
[3] is generated when
template_var
in [1] is visited, but the binding shouldn't be generated because the template variable is not specialized.[4] and [5] are generated when
specialized_var
in [2] is visited. [4] is okay becausespecialized_var
is just a global variable being assigned with a specialized template variable (i.e.,template_var<int>
). However, [5] should be either not generated or bem.attr("template_var_int") = chimera_test::template_var<int>
, which I'm not sure which one would be the right way. If we need to generate [5], note that the variable name should be mangled name (e.g.,template_var_int
) unless specified by config (also, we don't have a way to specify properties for variables).298 changes Chimera to skip generating [3] and [5].