[Bug]: Invalid symbol position given for intersection error types

[mindula]

Description

For the below scenario, we get VIRTUAL as the symbol.origin for MyDefaultError. Hence, MyDefaultError is not included in the list of visible symbols

Steps to Reproduce

type DefaultError distinct error;

public type MyErrorDetail record {
    string fileName;
};

type MyDefaultError DefaultError & error<MyErrorDetail>;

public function main() {
    My<cursor>
}

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

[mindula]

Related issue: #34509

[nipunayf]

The issue cannot seem to be reproduced with 2201.8.3.

[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.