Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The idomatic way to start a new side-effect-only task (that is: a task that returns no result) using the TPL in .NET 4.0 is using the following API:
Task Task.Factory.StartNew(Action<object>, object)
But why doesn’t the signature of this API look like this
Task Task.Factory.StartNew<T>(Action<T>, T)
or like this
Task Task.Factory.StartNew<T>(T, Action<T>)
Technical reasons or some other reason?
Okay, now that I understand the question properly 🙂
I believe it’s because this is meant to be a direct replacement for
ThreadPool.QueueUserWorkItem. I do agree that it seems somewhat odd… but if you’re using lambda expressions anyway, it’s probably easier to use the version that does take a state parameter (i.e.Actioninstead ofAction<object>) and just capture the value you’re interested in beforehand. It doesn’t help if you’re specifying the value and the function separately 🙁