Follow Rec!2977

This introduces the minimal changes for FunTuple to understand the optional return type of Functors::Optional<T>

Note that Rec!2977 (merged) does not yet change the behavior of e.g. MapRelInputToFunOuput. These Functors still return their constexpr invalid_value.

My proposal would be to merge Rec!2977 (merged) as is + this MR.
Then I can create a follow-up MR that removes the current usage of the constexpr invalid_value member to replace it with the new optional return type functionality.
But for that we also need to adapt FunTuple with the features to let us specify a default invalid value for a specific column in the tuple.

@amathad I am hoping you might have time to help with the latter? I already looked at FunTuple.cpp but wasn't sure where this should best be implemented.

added Functors enhancement labels

mentioned in merge request Rec!2977 (merged)

requested review from @amathad

assigned to @erodrigu and @pkoppenb

changed title from Follow rec 2977 to Follow Rec!2977

• [2022-06-30 13:52] Validation started with lhcb-master-mr#4903
• [2022-06-30 23:04] Validation started with lhcb-master-mr#4918

approved this merge request

/ci-test

resolved all threads

added ci-test-triggered label

merged

mentioned in commit 51a10f35

But for that we also need to adapt FunTuple with the features to let us specify a default invalid value for a specific column in the tuple. @amathad I am hoping you might have time to help with the latter? I already looked at FunTuple.cpp but wasn't sure where this should best be implemented.

@chasse I can certainly help with that. I have created an issue to get some input from Patrick and Eduardo on user interface. Both of the option there would require changes to FunTuple, so can take care of that.

resolved all threads