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]: No error when field access is used with a map of XML #39341

Closed
MaryamZi opened this issue Jan 24, 2023 · 1 comment · Fixed by #39600
Closed

[Bug]: No error when field access is used with a map of XML #39341

MaryamZi opened this issue Jan 24, 2023 · 1 comment · Fixed by #39600
Assignees
Labels
Planning/SwanLake2023 Temporary Label for issue to be fixed immediately. Points/2 Equivalent to two days effort Priority/High Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug userCategory/Compilation

Comments

@MaryamZi
Copy link
Member

Description

$title. Seems like xml is considered lax.

Steps to Reproduce

import ballerina/io;

public function main() returns error? {
    map<xml> m = {a: xml `foo`};
    xml x = check m.a; // no error
    io:println(x); // prints `foo`
}

Affected Version(s)

2201.3.2

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. Priority/High labels Jan 24, 2023
@ballerina-bot ballerina-bot added needTriage The issue has to be inspected and labeled manually userCategory/Compilation labels Jan 24, 2023
@hasithaa hasithaa added the Planning/SwanLake2023 Temporary Label for issue to be fixed immediately. label Feb 2, 2023
@lasinicl lasinicl added the Points/2 Equivalent to two days effort label Feb 2, 2023
@anupama-pathirage anupama-pathirage removed the needTriage The issue has to be inspected and labeled manually label Mar 17, 2023
@github-actions
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Planning/SwanLake2023 Temporary Label for issue to be fixed immediately. Points/2 Equivalent to two days effort Priority/High Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug userCategory/Compilation
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

6 participants