Functions: support optional outputs in multi-function

Sometimes not all outputs of a multi-function are required by the
caller. In those cases it would be a waste of compute resources
to calculate the unused values anyway. Now, the caller of a
multi-function can specify when a specific output is not used.
The called function can check if an output is unused and may
ignore it. Multi-functions can still computed unused outputs as
before if they don't want to check if a specific output is unused.

The multi-function procedure system has been updated to support
ignored outputs in call instructions. An ignored output just has no
variable assigned to it.

The field system has been updated to generate a multi-function
procedure where unused outputs are ignored.

1 files changed, 16 insertions, 0 deletions

diff --git a/source/blender/functions/tests/FN_field_test.cc b/source/blender/functions/tests/FN_field_test.cc
index 212b79e75d3..1c2d5c8eaad 100644
--- a/source/blender/functions/tests/FN_field_test.cc
+++ b/source/blender/functions/tests/FN_field_test.cc
@@ -5,6 +5,7 @@
 #include "FN_cpp_type.hh"
 #include "FN_field.hh"
 #include "FN_multi_function_builder.hh"
+#include "FN_multi_function_test_common.hh"
 
 namespace blender::fn::tests {
 
@@ -275,4 +276,19 @@ TEST(field, SameFieldTwice)
   EXPECT_EQ(varray2->get(1), 10);
 }
 
+TEST(field, IgnoredOutput)
+{
+  static OptionalOutputsFunction fn;
+  Field<int> field{std::make_shared<FieldOperation>(fn), 0};
+
+  FieldContext field_context;
+  FieldEvaluator field_evaluator{field_context, 10};
+  const VArray<int> *results = nullptr;
+  field_evaluator.add(field, &results);
+  field_evaluator.evaluate();
+
+  EXPECT_EQ(results->get(0), 5);
+  EXPECT_EQ(results->get(3), 5);
+}
+
 }  // namespace blender::fn::tests