List.find() causes segmentation fault

[Jan Silar]

When List.find is called and later fail() is called than the latter call causes segmentation fault.

To reproduce the problem add somewhere:

 _ := List.find({1,2,3,4}, findTestF);
  fail();

...

protected function findTestF
  input Integer inI;
  output Integer outI;
algorithm
  outI := match inI
    case 3
    then 9;
  end match;
end findTestF;

[Per Östlund]

Martin is working on this. Prefer using List functions that takes functions returning true or false instead of succeeding or failing though, it's more efficient since fail/matchcontinue costs more than checking a boolean. In this case we don't seem to have a specific List function that does the equivalent of List.find, but you could do e.g. someMapFunc(List.getMemberOnTrue({1, 2, 3, 4}, isThree)) (or just implement List.findOnTrue).

[Per Östlund]

List.find has now been replaced with List.mapFirst, and List.find is instead the old List.selectFirst. See 1981ce9. The issue in this ticket still needs to be fixed though.

[Martin Sjölund]

Fixed the bug in 9138159.