[Improvement]: Improve field access expression desugar #43769
Assignees
Labels
Fix/Crash
All issues caused by NPE, CCE, etc
Team/CompilerFE
All issues related to Language implementation and Compiler, this exclude run times.
Type/Improvement
Milestone
Comments
rdulmina
added
Team/CompilerFE
|
Desugared field access expression to the following structure // Before :
type A {
B b;
}
type B {
int c;
}
int? res = a?.b?.c
// After desugar :
any|error temp_result;
temp_result = a;
if temp_result !is error? {
temp_result = (<A> temp_result).b;
if temp_result !is error? {
temp_result = (<B> temp_result).c;
}
}
int? res = <int> temp_result;
|
This was referenced Jan 27, 2025
13 tasks
github-project-automation
bot
moved this from PR Sent
to Done
in Ballerina Team Main Board
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Description
Currently, the field access expression desugared in to match statement which cases lot of instructions when there is a large chain access of the field access expression. This could lead to unwanted
method to largeerrors at runtime.Need to find a better way of desugaring eg: Try to desugar into if statement.
Related internal issue: https://github.com/wso2-enterprise/internal-support-ballerina/issues/862
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered: