Without a citation that tells us exactly where you read that, we can only guess at the meaning I would interpret that phrase to mean that multiple LINQ methods act as a pipeline, i.e. Each piece of data flows through before the next one does For example: var numbers = new { 1, 2, 3 }; var results = numbers. Select(number => number * 2).
Where(number => number > 3) With eager evaluation, the execution would look like this: 1, 2, 3 -> Select -> 2, 4, 6 -> Where -> 4, 6 However, with deferred evaluation, each result is calculated when it is needed. This turns the execution of the methods "vertical" instead of "horizontal", executing all methods for each data item, then starting again with the next data item: 1 -> Select -> 2 -> Where -> nothing 2 -> Select -> 4 -> Where -> 4 3 -> Select -> 6 -> Where -> 6 Of course, this is not true for methods which operate on the whole set, such as Distinct and OrderBy All of the data items must "pool" there until execution can continue. For the most part, though, LINQ methods only ask for items from the source when they themselves are asked for another item.
Without a citation that tells us exactly where you read that, we can only guess at the meaning. I would interpret that phrase to mean that multiple LINQ methods act as a pipeline, i.e. Each piece of data flows through before the next one does.
For example: var numbers = new { 1, 2, 3 }; var results = numbers. Select(number => number * 2). Where(number => number > 3); With eager evaluation, the execution would look like this: 1, 2, 3 -> Select -> 2, 4, 6 -> Where -> 4, 6 However, with deferred evaluation, each result is calculated when it is needed.
This turns the execution of the methods "vertical" instead of "horizontal", executing all methods for each data item, then starting again with the next data item: 1 -> Select -> 2 -> Where -> nothing 2 -> Select -> 4 -> Where -> 4 3 -> Select -> 6 -> Where -> 6 Of course, this is not true for methods which operate on the whole set, such as Distinct and OrderBy. All of the data items must "pool" there until execution can continue. For the most part, though, LINQ methods only ask for items from the source when they themselves are asked for another item.
Thank you very much – user702769 Sep 26 at 18:41.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.