StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2230485
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2010-02-09T16:07:52.407
FavoriteCount
0
LastActivityDate
2010-02-09T16:14:59.363
LastEditDate
2010-02-09T16:14:59.363
LastEditorUserId
45914
OwnerUserId
45914
ParentId
2230451
PostTypeId
2
Score
33
ViewCount
0
LastEditorDisplayName
text
Body
<code>List<T>.ForEach</code> is looking for an <code>Action<T></code>. When you write <pre><code>n.ForEach(Console.WriteLine); </code></pre> what you have here is one of the members of the method group <code>Console.WriteLine</code> playing the role of an <code>Action<T></code>. The compiler will look for the best overload of <code>Console.WriteLine</code> that eats instances of <code>int</code>. In fact, it will use the overload <a href="http://msdn.microsoft.com/en-us/library/70x4wcx1.aspx" rel="noreferrer"><code>Console.WriteLine(int)</code></a>. It will then use this overload to play the role of an <code>Action<int></code>. For details on how this is done, see §6.6 of the specification (Method group conversions). However, when you write <pre><code>n.ForEach(i => Console.WriteLine(i)); </code></pre> we actually have a very different <code>Action<int></code> In the first case, the <code>Action<int></code> was <code>Console.WriteLine(int)</code>. Here, the <code>Action<int></code> is equivalent to you having written <pre><code>public static void DoSomething(int i) { Console.WriteLine(i); } </code></pre> and then <pre><code>n.ForEach(DoSomething); </code></pre> (Of course, the compiler has to go through the same method group process as described above to figure out what is meant by <code>DoSomething</code>). The point is that in the first case the <code>Action<int></code> is <code>Console.WriteLine(int)</code>. However, in the second case the <code>Action<int></code> is a middle man (the lambda expression) that itself will call <code>Console.WriteLine(int)</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC# method group strangeness
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USjason
UserOwnerUserId
1. USjason
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POC# method group strangeness
 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
 VTUpMod
CommentsPostId
1. CO++ for imagery of the compiler "eating" an overload of Console.WriteLine!
 singulars
 PostPostId
 PO
 UserUserId
 USTad Donaghe
2. COVery nicely articulated. Thank you!
 singulars
 PostPostId
 PO
 UserUserId
 USKeith
3. CONice explanation.
 singulars
 PostPostId
 PO
 UserUserId
 USAdriaan Stander

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.