'Reverse' pipeline operator proposal. about mond HOT 3 CLOSED

I'm not sure what problem this is meant to solve, could you come up with a better example?

from mond.

As I mentioned above, it's more niche than problem-solver. Closer to syntax sugar than anything else, mainly allowing an anonymous function or lambda to be separated from the argument list of a function call, which would be most useful for array prototype functions like map, filter, and reduce, which take a callback as their only argument and apply it to each element of the sequence.

Another example could be a slightly more complex filtering algorithm to collect a list of file names.

// List all .cs files in the current directory
// that don't contain pre-processor directives
var files = Directory.getFiles( "./*.cs" ).filter() <|
fun( name ) {
    var lines = File.readAllText( name )         // Read file contents into memory
                    .split( "\n" )               // Split on LF
                    .map( line -> line.trim() ); // Map each line through a lambda
                                                 // that trims all whitespace off both ends

    foreach( var line in lines ) { // Iterate the sanitized lines
        if( line.startsWith( "#" ) )
            return false; // Reject the file if any of the lines start with '#'
    }

    return true; // Otherwise accept the file.
};

from mond.

I'm still not sure about it. The only advantage I see from this is the function call's closing parenthesis can stay with the call. I don't think it's very useful to chain <| either.

If there was a better example for this I'd be up for it, but right now it looks like it only lets you type a bit more to keep the closing parenthesis with the call.

from mond.