在下面的代码中,由于接口的关系,类 下面我使用了 有没有更好的办法?
using System.Threading.Tasks;
namespace MyAsyncTest
{
internal interface IFooFace
{
Task WillBeLongRunningAsyncInTheMajorityOfImplementations();
}
/// <summary>
/// An implementation, that unlike most cases, will not have a long-running
/// operation in 'WillBeLongRunningAsyncInTheMajorityOfImplementations'
/// </summary>
internal class LazyBar : IFooFace
{
#region IFooFace Members
public Task WillBeLongRunningAsyncInTheMajorityOfImplementations()
{
// First, do something really quick
var x = 1;
// Can't return 'null' here! Does 'Task.Delay(0)' have any performance considerations?
// Is it a real no-op, or if I call this a lot, will it adversely affect the
// underlying thread-pool? Better way?
return Task.Delay(0);
// Any different?
// return Task.Run(() => { });
// If my task returned something, I would do:
// return Task.FromResult<int>(12345);
}
#endregion
}
internal class Program
{
private static void Main(string[] args)
{
Test();
}
private static async void Test()
{
IFooFace foo = FactoryCreate();
await foo.WillBeLongRunningAsyncInTheMajorityOfImplementations();
return;
}
private static IFooFace FactoryCreate()
{
return new LazyBar();
}
}
}
今天,我建议使用Task.CompletedTask来实现这一点。
净价4.6:
使用
为了补充ReedCopsey关于使用
public static class TaskExtensions
{
public static readonly Task CompletedTask = Task.FromResult(false);
}
使用
NET Framework(V4.6)的最新版本通过
Task completedTask = Task.CompletedTask;
接受答案中的
从4.6开始,
两者的缓存性质都不能保证保持不变,但是作为仅依赖于实现的优化(也就是说,如果实现更改为仍然有效的内容,它们仍然可以正常工作),使用