diff options
author | Hans Goudey <h.goudey@me.com> | 2021-09-07 04:43:21 +0300 |
---|---|---|
committer | Hans Goudey <h.goudey@me.com> | 2021-09-07 04:43:21 +0300 |
commit | cffd4a7ccf7dcf0d92d1b2392ac5adba9a965cdb (patch) | |
tree | 97d891b0b9df50e5eca53773d0eca45d3d0a0ca6 | |
parent | 2012469accc617326220df7fd5b0d00c07961f16 (diff) |
Cleanup: Add comment about reusing span for input and output
-rw-r--r-- | source/blender/nodes/geometry/nodes/node_geo_point_translate.cc | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/source/blender/nodes/geometry/nodes/node_geo_point_translate.cc b/source/blender/nodes/geometry/nodes/node_geo_point_translate.cc index ad91cb2d377..48778532789 100644 --- a/source/blender/nodes/geometry/nodes/node_geo_point_translate.cc +++ b/source/blender/nodes/geometry/nodes/node_geo_point_translate.cc @@ -90,7 +90,9 @@ static void execute_on_component(GeometryComponent &component, /* Add an add operation field on top of the provided translation field, which can be evaluated * directly into the position virtual array. That way, any optimizations can be done more - * generally for the whole evaluation system. */ + * generally for the whole evaluation system. In the general case it may not work to share the + * same span for the input and output of an evaluation, but in this case there there is only one + * output, so it is fine. */ static const fn::CustomMF_SI_SI_SO<float3, float3, float3> add_fn = { "Add", [](float3 a, float3 b) { return a + b; }}; std::shared_ptr<fn::FieldOperation> add_operation = std::make_shared<fn::FieldOperation>( |