[Bug]: Code hangs when using field of type array or tuple in the order by clause of a query

[poorna2152]

Description

Consider the following code,

import ballerina/io;
import ballerina/time;

type A record {|
    time:Utc t;
    int i;
    string s;
|};

public function main() returns error? {
    A[] lotOfA = [
        {i: 1, s: "s1", t: check time:utcFromString("2007-12-03T10:15:30.00Z")},
        {i: 1, s: "s1", t: check time:utcFromString("2008-12-03T10:15:30.00Z")},
        {i: 1, s: "s1", t: check time:utcFromString("2004-12-03T10:15:30.00Z")},
        {i: 1, s: "s1", t: check time:utcFromString("2012-12-03T10:15:30.00Z")}
    ];

    string[] lotOfS = from A a in lotOfA
        where a.i == 1
        order by a.t descending
        select a.s;
    io:println(lotOfS);
}

Following code hangs when running. This should not throw an compiler error because it should be possible to use a field of type time:Utc to order.

Steps to Reproduce

No response

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[poorna2152]

The issue lies in using a array type as the order-key in the order clause. This is reproducible with the following code.

import ballerina/io;

type A record {|
    [int] t;
    int i;
    string s;
|};

public function main() returns error? {
    A[] lotOfA = [
        {i: 1, s: "s1", t: [5]},
        {i: 1, s: "s1", t: [1]},
        {i: 1, s: "s1", t: [0]},
        {i: 1, s: "s1", t: [4]}
    ];

    string[] lotOfS = from A a in lotOfA
        where a.i == 1
        order by a.t descending
        select a.s;
    io:println(lotOfS);
}

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.