StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8061370
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-09T06:51:38.473
FavoriteCount
0
LastActivityDate
2011-11-09T06:56:58.827
LastEditDate
2011-11-09T06:56:58.827
LastEditorUserId
22656
OwnerUserId
22656
ParentId
8061345
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
TL;DR: The performance difference here is almost certainly insignificant in a real application, and there's a more readable way of achieving the same result anyway. It's still interesting to see the differences in compiled code though. Assuming the full code is actually: <pre><code>int result = 0; foreach (int i in intList) { result += i; } </code></pre> vs <pre><code>int result = 0; intList.ForEach(i => result += i); </code></pre> then the first form is rather simpler in terms of what gets generated - you'll end up with just a local variable, code to iterate over the list (using <code>List<T>.Enumerator</code>) and IL which adds the value to the local variable. The second form will need to generate a new class with an instance variable for <code>result</code>, along with a method to be used as the delegate. The code will be converted to: <pre><code>CompilerGeneratedClass tmp = new CompilerGeneratedClass(); tmp.result = 0; Action<int> tmpDelegate = new Action<int>(tmp.CompilerGeneratedMethod); intList.ForEach(tmpDelegate); </code></pre> On top of that there's the philosophical differences between <code>foreach</code> and <code>ForEach</code> which <a href="http://blogs.msdn.com/b/ericlippert/archive/2009/05/18/foreach-vs-foreach.aspx">Eric Lippert has written about</a>. Personally I'd just use LINQ though: <pre><code>int result = intList.Sum(); </code></pre> I doubt that the performance differences will actually be a bottleneck in real code, but the LINQ version is the clearest IMO, and that's always a good thing.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO"foreach" VS "List<T>.Foreach"...which wins
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJon Skeet
UserOwnerUserId
1. USJon Skeet
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PO"foreach" VS "List<T>.Foreach"...which wins
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.