Audit treatment of Nothing in lowering code

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • QO 2023-01-23
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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?

            Assignee:
            Davis Haupt (Inactive)
            Reporter:
            Hana Pearlman
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: