[Bug]: The put method does not handle hash-collided keys

[nipunayf]

Description

The current implementation of the put method in the table language library does not handle the case when there are two distinct keys with the same hash code. For instance, the output of the following code is [{"k":"10"},{"k":5},{"k":0},{"k":-31},{"k":100.05},{"k":30}] when it should be [{"k":"10"},{"k":5},{"k":null},{"k":0},{"k":-31},{"k":100.05},{"k":30}].

import ballerina/io;

public function main() {
    table<record {readonly int|string|float? k;}> key(k) tbl1 = table [{k: "10"}];

    tbl1.put({k: 5});
    tbl1.put({k: ()});
    tbl1.put({k: -31});
    tbl1.put({k: 0});
    tbl1.put({k: 100.05});
    tbl1.put({k: 30});

    io:println(tbl1);
}

However, the add method of the table language library works as expected. For instance, the following code generates the expected result.

import ballerina/io;

public function main() {
    table<record {readonly int|string|float? k;}> key(k) tbl1 = table [{k: "10"}];

    tbl1.add({k: 5});
    tbl1.add({k: ()});
    tbl1.add({k: -31});
    tbl1.add({k: 0});
    tbl1.add({k: 100.05});
    tbl1.add({k: 30});

    io:println(tbl1);
}

Steps to Reproduce

Run the following Ballerina code.

import ballerina/io;

public function main() {
    table<record {readonly int|string|float? k;}> key(k) tbl1 = table [{k: "10"}];

    tbl1.put({k: 5});
    tbl1.put({k: ()});
    tbl1.put({k: -31});
    tbl1.put({k: 0});
    tbl1.put({k: 100.05});
    tbl1.put({k: 30});

    io:println(tbl1);
}

Affected Version(s)

Ballerina 2201.8.1 (Swan Lake Update 8)

OS, DB, other environment details and versions

OS: macOS 14.0 23A344
Java: openjdk version "17.0.8" 2023-07-18

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

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