On Readability, Thought Process, and Coding Fluency

[blhsing (Ben Hsing)]

@tzengshinfu

When we think while coding, our order usually goes like this:

1. Identify the variable (possibly the result of a previous step)
2. Decide what to do with it (function/operator)
3. Get the output

The thought process feels like this:
a + b = c; c - d = e; e * f = g; g / h = answer
It flows from left to right, with input on the left and output on the right, all in the same direction.

You might be interested in voicing your support for a pipeline syntax proposed in the ongoing discussion, where with my proposed syntax plus a later revision to position a piped object as the first argument by default, your throught process above can be better expressed as:

from operator import *

a + b |> sub(d) |> mul(f) |> div(h) as answer # or a |> add(b) |> sub(d) ...

or:

a + b |> _ - d |> _ * f |> _ / h as answer

Like I mentioned in the post, the proposed syntax is all about giving people the option to write code that better fits their mental model.