We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is some cases that looks more natural to keep the lambda argument definition at the same level of backpipe operator
testCase "foo" <| fun _ -> let subject = true Expect.isTrue subject "I compute, therefore I am."
Today I think that the accepted way would be only:
This form gives a more "function body" look to some expressions, which plays well with this kind of definitions (eg. Expecto)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There is some cases that looks more natural to keep the lambda argument definition at the same level of backpipe operator
Today I think that the accepted way would be only:
This form gives a more "function body" look to some expressions, which plays well with this kind of definitions (eg. Expecto)
The text was updated successfully, but these errors were encountered: