We often had to use two FieldEvaluator instances to first evaluate the selection and then the remaining fields. Now both can be done with a single FieldEvaluator. This results in less boilerplate code in many cases.
Performance is not affected by this change. In a separate patch we could improve performance by reusing evaluated sub-fields that are used by the selection and the other fields.
Details
Details
Diff Detail
Diff Detail
- Repository
- rB Blender
Event Timeline
Comment Actions
Looks like a good change to me. Apart from the possible future sharing of intermediate values, less boilerplate code is nice.
| source/blender/functions/FN_field.hh | ||
|---|---|---|
| 342–343 | Might be helpful to say something like "Only the elements selected by both this selection *and* the selection provided in the constructor are calculated." | |