Is there a chance for the pipeline operator feature to be implemented in C#?

[GaN8373]

I checked #74 and #96 , but couldn't find any intention to implement it. I would like to know if it will be implemented in CS in the future.
I prefer this style:

var x = "123";
x +"1" |> Convert.ToInt32 var vi32
    |> value > 100 ? 100 : 1
    |> Console.WriteLine(value + vi32);

Console.WriteLine(vi32);

// unwrap code:
var _anonymouse = x +"1";
var vi32 = Convert.ToInt32(_anonymouse);
var _anonymouse = vi32 > 100 ? 100 : 1;
Console.WriteLine(_anonymouse + vi32);

Console.WriteLine(vi32);
···
future idea:
1. Value can point to the previous result
2. The result can be named by var
3. Named results can be used outside the pipeline

[iam3yal]

@GaN8373 In what language did you use it? because it seems like some people in the links people still don't get the point of the operator but weirdly enough they prefer to write their code in this way...

[timcassell]

I used it in Elixir. Would love for C# to get it.

[GaN8373]

@GaN8373 In what language did you use it? because it seems like some people in the links people still don't get the point of the operator but weirdly enough they prefer to write their code in this way...

The language I often use for pipeline operations is shell.

This made me accustomed to sequential operations. For example, in a chain of method calls, I had to write a(), then declare its return value as a variable. Then repeat these steps to process it into nested calls like d(c(b(a()))); or it would become: var a = a(); var b = b(a); ...

Whereas the pipe operator (|>) allows me to follow my train of thought: taking the result of a() and then processing it with b(). Resulting in the pipe operation: a() |> b().

[iam3yal]

@GaN8373 The reason I asked is because the code in the OP doesn't really match this pattern d(c(b(a()))); .

[GaN8373]

@GaN8373 The reason I asked is because the code in the OP doesn't really match this pattern d(c(b(a()))); .

My apologies, it seems my technical understanding was insufficient. I mistakenly thought two different concepts were the same.

[KennethHoff]

I don't know if the pipeline operator befits C#, but I would appreciate a lambda shorthand like what F# has:

// Long form
IEnumerable<Person> persons = ...;

Person oldest = persons.MaxBy(x => x.Age)


// Short form
IEnumerable<Person> persons = ...;

Person oldest = persons.MaxBy(_.Age)