mixed notation does not work for records and sets

Summary

In TTCN-3 it shall be possible to use mixed notation to assign a value to record, and set type data element. TITAN however, does not allow this.

Steps and/or TTCN-3 code to reproduce

Create a module, include this in it:

type set mySet{
  integer field1,
  charstring field2,
  boolean field3,
  float field4
}

type record myRecord{
  integer field1,
  charstring field2,
  boolean field3,
  float field4
}

testcase mixed_notation_set_record() runs on ct_empty{
  var mySet v1:= {1,"a",field4:=2.3,field3:=false};
  var myRecord v2 := {1,"a",field3:=false,field4:=2.3};
  setverdict(pass);
}

Compile it

What is the current bug behavior?

Two errors are generated, one for the set and one for the record.

What is the expected correct behavior?

The testcase should pass. Maybe changing the order of field3 and field4 in the assignment of the set value is not allowed in TTCN-3, in case of mixed notation, but this is not specified in the standard. So try it with this code piece too:

var mySet v1:= {1,"a",field3:=false,field4:=2.3};

Relevant logs and/or screenshots

Possible fixes

Titan version

8.1.0

Platform details (OS type and version)

Microsoft Windows 10 Enterprise 10.0.19042

/cc @aknappqwt