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
{{ message }}
This repository was archived by the owner on Sep 13, 2022. It is now read-only.
The first framework that provides NetStandard 2.1 is NetCoreApp 3.0.
So NetStandard 2.1 have no limitations in adding API from .NetCoreApp 3.0
Despite some useful TheadPool methods are missing in the .Net Standard 2.1.
For example:
public static bool UnsafeQueueUserWorkItem<TState>(Action<TState> callBack, TState state, bool preferLocal)
these methods are mandatory for the efficient implementation of the IValueTaskSource
Real life case:
The ManualResetValueTaskSourceCore<TResult> included into NetStandard 2.1, but if you try to copy-paste its sources and modernize for your needs
you will unable to do it being NetStandard 2.1 library, you need to upgrade to NetCoreApp 3.0.
If upgrade to NetCoreApp 3.0 is unacceptable then you need to have inefficient implementation - very disappointing problem where you don't expect it.
The text was updated successfully, but these errors were encountered:
The first framework that provides NetStandard 2.1 is NetCoreApp 3.0.
So NetStandard 2.1 have no limitations in adding API from .NetCoreApp 3.0
Despite some useful
TheadPool
methods are missing in the .Net Standard 2.1.For example:
these methods are mandatory for the efficient implementation of the
IValueTaskSource
Real life case:
The
ManualResetValueTaskSourceCore<TResult>
included into NetStandard 2.1, but if you try to copy-paste its sources and modernize for your needsyou will unable to do it being NetStandard 2.1 library, you need to upgrade to NetCoreApp 3.0.
If upgrade to NetCoreApp 3.0 is unacceptable then you need to have inefficient implementation - very disappointing problem where you don't expect it.
The text was updated successfully, but these errors were encountered: