Dulmina Renuke

The above example in the issue works without any issue in the current implementation because although the `l` is defined after the type `T1`, when we codegen we populate the...

Changes are done. 13 jballerina unit tests are filing ATM. Will send a PR soon. Below are some failing cases. 1. The below sample fails with `java.lang.NullPointerException: Cannot read field...

Fixed with #43596

Closing this PR since if we remove the typedesc class we need to find a way to preserve the value class for the corresponding typedesc. Hence we decided to keep...

Changes are done. 13 jballerina unit tests are filing ATM. Will send a PR soon. Below are some failing cases. 1. The below sample fails with `java.lang.NullPointerException: Cannot read field...

Large method issue is due to how we create typedesc statements from the Desugar. Consider the below sample. ```bal public function main() { [record {|string name; int age;|}, record {|string...

Another reson that could cause large method error Consider the below sample ```bal public function main() { [record {||}, record {||}] a = [{}, {}]; a = [{}, {}]; }...

Large method issues were fixed by [Compress arguments into a tuple if the split method contains large number of args](https://github.com/ballerina-platform/ballerina-lang/pull/43596/commits/810bcc660b1f1e554d2dde7dc3388a96b202acaf) [810bcc6](https://github.com/ballerina-platform/ballerina-lang/pull/43596/commits/810bcc660b1f1e554d2dde7dc3388a96b202acaf)

[UPDATE]: Code review conducted. Waiting for reviews. Created issues to address future work #44073 #44074

[UPDATE]: Final round review in-progress