rfc:switch_expression

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
rfc:switch_expression [2020/03/28 01:42] – List Michał as an author ilijatovilorfc:switch_expression [2020/03/28 11:31] – Minor rewording ilijatovilo
Line 120: Line 120:
 </code> </code>
  
-The fallthrough behavior can't reasonably be changed in the ''switch'' statement because it would break a lot of code. However this RFC porposes allowing multiple conditions per ''case'' so that the intention of running the same code can be expressed more clearly. The ''switch'' expression resolves this issue exactly as described above. There is an implicit ''break'' added after each ''case''. Like with the statement multiple ''case'' conditions can be separated by a '',''.+The fallthrough behavior can't reasonably be changed in the ''switch'' statement because it would break a lot of code. However this RFC porposes allowing multiple conditions per ''case'' so that the intention of running the same code can be expressed more clearly. The ''switch'' expression resolves this issue exactly as described above. There is an implicit ''break'' added after each ''case''. Like with the statement multiple ''case'' conditions can be separated by a comma.
  
 ==== Inexhaustiveness ==== ==== Inexhaustiveness ====
Line 171: Line 171:
  
 <code php> <code php>
-$x = switch ($y) {}+$x = switch ($y) {};
 // instead of // instead of
-$x = $y switch {}+$x = $y switch {};
 </code> </code>
  
Line 189: Line 189:
  
 ===== "Why don't you just use x" ===== ===== "Why don't you just use x" =====
-The have been some comments on how you can already achieve the same result.+There have been some comments on how you can already achieve the same result.
  
 ==== if statements ==== ==== if statements ====
rfc/switch_expression.txt · Last modified: 2020/04/12 00:04 by ilijatovilo

Page Tools