Trying to fix switch EOG

[oxisto]

Not sure, if this really the "correct" solution. @konradweiss should probably have another look at this.

Fixes #1568

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[konradweiss]

Yes, this should be the correct fix. When implementing the EOG for the switch statement I thought the assumption that one case always has to match, therefore enforcing the presence of a default if the switches do not map exhaustively.

This means with this PR we accept having an incorrect EOG edge if the cases alone handle all possible values of the expression in the switch but now support switch statements that don't enforce a default if the cases do not cover the expressions value exhaustively.

[konradweiss]

This should be an adequate improvement although it adds in incorrect edge if there is no default case but all case: cases exhaustively handle the selector expression.

[oxisto]

This should be an adequate improvement although it adds in incorrect edge if there is no default case but all case: cases exhaustively handle the selector expression.

Hmm any idea how we can do that?