Implementation of IHandle<T> for synchronous handlers

In earlier versions of Caliburn Micro, we used to have separate implementations of IHandle (and IHandleWithTask). However, in 4.x, this seems to be changed and replaced with a single interface.

public interface IHandle<TMessage>
{
       Task HandleAsync(TMessage message, CancellationToken cancellationToken);
}

One issue I find with this approach is that in the scenarios when there are no asynchronous calls in the handlers, the naming convention looks out of place with the Async suffix. The code style checkers would show these as warnings as well, leaving a clutter of warnings in the solution.

Wouldn’t it be better to bring back the IHandleWithTask to separate the different implementations ?

[Jammyo]

I don’t think putting both functions into IHandle is an option because then users are forced to implement one no-op for each handler (unless I misunderstood the suggestion?). To the original point, in scenarios with no asynchronous calls, code style checkers should only show a warning if the async keyword is used. Setting the handler as the following should work fine:

public Task HandleAsync(MyEvent @event, CancellationToken cancellationToken)
{
    // Handle event
    return Task.CompletedTask;
}

[vb2ae]

C#8 has support to add default implementations to methods. Updated the IHandle interface to add have default implementation for .net 5, .net 6, and .net core 3.1 #780