Match switch optimization causes issues with guards

[Per Östlund]

Guards on cases in a match rely on the fact that the generated code is a for-switch. When a match is optimized into a switch this no longer works correctly, since the switch won't try another case if the guard is false. Example:

uniontype U
  record INT
    Integer value;
  end INT;

  record REAL
    Real value;
  end REAL;
end U;

function greaterThanZero
  input U u;
  output Boolean b;
algorithm
  b := match(u)
    case INT() guard(u.value > 0) then true;
    case REAL() guard(u.value > 0) then true;
    else false;
  end match;
end greaterThanZero;

function test
algorithm
  greaterThanZero(INT(-2));
end test;

This will simply fail, instead of returning false as expected.

[Martin Sjölund]

I think probably switch with guards should not be allowed to exist ;)
Or we need to add goto on guard fail...

[Martin Sjölund]

Fixed in c93aec7

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Milestone renamed