Replies: 3 comments
-
Without much contemplation though, for people without exposure to both SQL and functional programming, I think the learning curve might be comparable (if that's one of the factors to consider.) |
Beta Was this translation helpful? Give feedback.
0 replies
-
For those who don't have idea about two syntaxes of LINQ: https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/linq/query-syntax-and-method-syntax-in-linq. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently in our code base we only use functional-style LINQ statements only. As far as we're concerned, there isn't a critical reason why we're not using SQL-style LINQ statements. One of the advantages with SQL-style LINQ statements is that we can use
let
which allows us to allocate an intermediate value for manipulation in the LINQ chain. For example:To do similar things with functional-style LINQ statements, values must be packed into tuples or the statement must be broken into parts with loops and such. However, the syntax of SQL-style LINQ is kind of alienated with the rest of C# syntax, and might require some familiarizing.
For this, I would like to discuss:
Beta Was this translation helpful? Give feedback.
All reactions