You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: it seems that ValueTask and ValueTask<T> methods are forced to completion, and thus go through InterceptSynchronous. Maybe that's the reason why we've got this discrepancy.
The discrepancy is because this library does not consider ValueTask and ValueTask<T> (it predates them by a few years) and it determines whether a method is asynchronous based on it returning Task or Task<T>.
PRs are always welcome. Almost all the secret source is in the class AsyncDeterminationInterceptor, that's where you should start looking if you want support for ValueTask and ValueTask<T>.
The types
ValueTask
andValueTask<T>
are not intercepted with the async interceptor, always going through theInterceptSynchronous
method.The text was updated successfully, but these errors were encountered: