vavr-io/vavr

Hi
I think in terms of overhead (each andThen creates a new lambda function) and debugging (you can step between function calls with just one call can see the result of all previous functions) is better compared to the second method.
With variable names I have two problems

1. the scope of the result of the function becomes greater

   val result1 = fn1(value)
   val result2 = fn2(result1)
   /*both value and result1 can be passed here if types match*/
   val result3 = fn3(result2)

2. it does not always provide extra information

   pipe(n, add(1),  times(3))

3. java punishes using variables because you can only declare variables in a block and a block is not an expression and not even consistent:

    final Foo foo;
    {
        val added = add(n);
        foo = times(3);
    }
    // but in lambda we in use return
    n => {
        val added = add(n);
        return times(3);
    }
   
    // you may declare a method, but the definition almost as long as the method itself
    private static Foo getFoo(Bar n) {
        val added = add(n);
        return times(3);
    }