type resolution problem when using RecordAssembler
Using RecordAssembler can cause type resolution to fail. Attached are two models that demonstrate the problem.
In rec-assembler-1.xml, a type resolution error will usually, but not always, occur when you run it.
In rec-assembler-2.xml, the second RecordAssembler actor is replaced with an Expression actor that constructs the same record, and no type resolution error occurs.
#2 Updated by Marten Lohstroh about 5 years ago
- % Done changed from 0 to 100
- Assignee changed from Daniel Crawl to Marten Lohstroh
- Status changed from New to Closed
The arbitrary order in which Mogensen's algorithm resolves type constraints seemed to trigger non-deterministic type errors due to an error in ParseTreeTypeInference.visitMethodCallNode(). Changes were made in revision 71540 and the supplied model now runs without errors.