Closed arcanefoam closed 9 months ago
Thanks for reporting this Horacio. I've attached a minimal working example that demonstrates the issue.
Until this gets fixed, you can use .equivalent()
instead of ::=
as a workaround, i.e. c.other = a.equivalent();
in your example.
Description
When importing an EOL script into ETL, the Special Assignment Operator semantics are not respected when executing the code in the EOL script.
Example
Current Behavior
The statement
c.other ::= a
, will try to assigna
toc.other
, resulting in a cast error.Expected Behavior The statement
c.other ::= a
, will assigna
's equivalent toc.other
.