Array indexing generates bad code

[Adrian Pop]

We generate bad code for this model:

function f
  input Real t;
  output Boolean arr[4];
algorithm
  arr[{1, 2}] := {true, false};
  arr[{3, 4}] := {false, true};
end f;

model ArrayIndexing
  Boolean gates[4](each start = false);
equation
  gates = f(time);
end ArrayIndexing;

[Mahder Alemseged Gebremedhin]

Fixed in r24930. Test cases added in r24947.

[Dietmar Winkler]

It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.

[Martin Sjölund]

Removing the pre1.9.4 milestone in favor of 1.9.4.