Revisit flags set to differentiate between the different kinds of fields of a record

[SasinduDilshara]

Description

Currently defaultable fields in record types does not contain Field and DEFAULTABLE_PARAM field flags.
Please refer to this comment also. #37491 (comment).

type CustomRecord record {
    readonly int id = 1;  // id field does not contain `Field` and `DEFAULTABLE_PARAM` field flags. Need to add `DEFAULTABLE_PARAM` and `Field` flags
    string name;
};

function testDefaultValueFieldAsKeyField2() {
    table<CustomRecord> key (id) tb = table [
        {id: 2, name: "Amy"}
    ];
}

Steps to Reproduce

No response

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Labels

CompilerFE

Related issue(s) (optional)

#33298

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[MaryamZi]

The isn't a bug. DEFAULTABLE_PARAM is specifically for defaultable parameters.

The improvement we can do is revisiting how we model the three different kinds of individual fields of a record:

• required field without a default value
• required field with a default value
• optional field

Right now, the flags are set as follows.

• required field without a default value - REQUIRED
• optional field - OPTIONAL

A required field with a default value is then identified by the absence of both flags (REQUIRED and OPTIONAL). But this isn't exactly clear with spec terms.

This issue is to see how we can improve the flags (probably have three different flags to reflect the three kinds).