Skip to content
This repository was archived by the owner on Sep 13, 2022. It is now read-only.

Incomplete ThreadPool API in NetStandard 2.1 comparing to NetCoreApp 3.0+ #1700

Closed
dmitriyse opened this issue Feb 9, 2020 · 2 comments
Closed

Comments

@dmitriyse
Copy link

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.

@benaadams
Copy link
Member

/cc @stephentoub @terrajobst

@terrajobst
Copy link

Closing as not planned, as .NET Standard is considered complete.

@terrajobst terrajobst closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants