Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Invalid error when using a spread field with a never-typed optional field #41363

Closed
MaryamZi opened this issue Sep 8, 2023 · 1 comment · Fixed by #41680
Closed

[Bug]: Invalid error when using a spread field with a never-typed optional field #41363

MaryamZi opened this issue Sep 8, 2023 · 1 comment · Fixed by #41680
Assignees
Labels
Priority/High Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug
Milestone

Comments

@MaryamZi
Copy link
Member

MaryamZi commented Sep 8, 2023

Description

$title.

Steps to Reproduce

type Employee record {|
    int id;
    string name;
|};

public function main() {
    record {|
        int id;
        string name;
        never dept?;
    |} rec = {
        name: "Joy",
        id: 1023
    };
    Employee _ = {...rec}; // error: undefined field 'dept' in record 'Employee'

    Employee e = rec; // OK
    Employee _ = {...e}; // OK
}

Affected Version(s)

2201.7.2, 2201.8.0-SNAPSHOT

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

@MaryamZi MaryamZi added Type/Bug Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. labels Sep 8, 2023
Copy link

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.

@gimantha gimantha added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Nov 29, 2023
@poorna2152 poorna2152 added this to the 2201.9.0 milestone Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority/High Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants