-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Query Optimization
-
Fully Compatible
-
QO 2023-01-23
This ticket is to audit treatment of Nothing in the lowering code to understand where & why we need fillEmpty and to see if handling of Nothing is missing anywhere.
For example, when lowering PathComposeA/M in the Filter context, we use fillEmpty on the first child path, which is the input to an If expression. Is this necessary? Should we have a fillEmpty on the second path as well?