rfc:pipe-operator-v2

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
rfc:pipe-operator-v2 [2021/07/05 15:58] – References are no longer allowed crellrfc:pipe-operator-v2 [2021/07/06 17:02] – Bring back references crell
Line 140: Line 140:
 ===== Additional semantics ===== ===== Additional semantics =====
  
-Functions that accept their first parameter by reference are not allowed.  Functions that return by reference are not allowed.  As the whole point of pipes is to pass values along from one function to the nextreferences are of little value.+Functions that accept their first parameter by reference are allowed, as are functions that return by reference.  They will behave semantically the same as if they were passed a variable by reference or returned a variable by reference via a "normal" call.  In practicehowever, reference variables are of little use in pipes so this is more of a design artifact than design intent.
  
 When evaluating a pipe, the left-hand side is fully evaluated first, then the right-hand side, then the right-hand side is invoked using the left-hand side.  That is, evaluation is strictly left-to-right. When evaluating a pipe, the left-hand side is fully evaluated first, then the right-hand side, then the right-hand side is invoked using the left-hand side.  That is, evaluation is strictly left-to-right.
rfc/pipe-operator-v2.txt · Last modified: 2021/07/20 15:34 by crell