StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19869878
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-08T22:45:06.483
FavoriteCount
0
LastActivityDate
2013-11-08T22:54:18.027
LastEditDate
2013-11-08T22:54:18.027
LastEditorUserId
238419
OwnerUserId
2362613
ParentId
11695886
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
When you pass a <code>Func<TResult></code> into a method <code>Run<TResult>(Func<TResult>)</code> you don't have to specify the generic on the methodcall because it can infer it. Your lambda does that inference. However, your function is not actually a <code>Func<TResult></code> whereas the lambda was. If you do <code>Func<Int32> f = MyIntReturningMethod</code> it works. Now if you specify <code>Task.Run<Int32>(MyIntReturningMethod)</code> you would expect it to work also. However it can't decide if it should resolve the <code>Func<Task<TResult>></code> overload or the <code>Func<TResult></code> overload, and that doesn't make much sense because its obvious that the method is not returning a task. If you compile something simple like follows: <pre><code>void Main() { Thing(MyIntReturningMethod); } public void Thing<T>(Func<T> o) { o(); } public Int32 MyIntReturningMethod() { return (5); } </code></pre> the IL looks like this.... <pre><code>IL_0001: ldarg.0 IL_0002: ldarg.0 IL_0003: ldftn UserQuery.MyIntReturningMethod IL_0009: newobj System.Func<System.Int32>..ctor IL_000E: call UserQuery.Thing </code></pre> (Some of the extra stuff is from LINQ Pad's additions... like the UserQuery part) The IL looks identical as if you do an explicit cast. So it seems like the compiler does't actually know which method to use. So it doesn't know what cast to create automatically. You can just use <code>Task.Run<Int32>((Func<Int32>)MyIntReturningMethod)</code> to help it out a bit. Though I do agree that this seems like something the compiler should be able to handle. Because <code>Func<Task<Int32>></code> is not the same as <code>Func<Int32></code>, so it doesn't make sense that they would confuse the compiler.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POc# .net why does Task.Run seem to handle Func<T> differently than other code?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBlueRaja - Danny Pflughoeft
UserOwnerUserId
1. USLameCoder
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
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.