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
Is your feature request related to a problem? Please describe.
Until #1424 is resolved, the library seems to target Netstandard2.0. If I understood the discussion correctly for v8 the team is willing to rediscuss the TFMs. Until then, is it reasonable to Polyfill language gaps with something like https://github.com/Sergio0694/PolySharp or https://github.com/SimonCropp/Polyfill/ (my preference but would require LangVersion=latest)? This would allow the library authors to use polyfilled language features even with Netstandard2.0.
Those libs would also polyfill nullable annotations, which means the Nullable reference could be removed.
Describe the solution you'd like
Using a Polyfilling library
Describe alternatives you've considered
Leaving as is
Additional context
No response
The text was updated successfully, but these errors were encountered:
Not strictly necessary but it opens the door for the lifetime of v7 to use newer language features in Netstandard2.0. The alternative is to manually polyfill every use case when it is needed.
Is your feature request related to a problem? Please describe.
Until #1424 is resolved, the library seems to target Netstandard2.0. If I understood the discussion correctly for v8 the team is willing to rediscuss the TFMs. Until then, is it reasonable to Polyfill language gaps with something like https://github.com/Sergio0694/PolySharp or https://github.com/SimonCropp/Polyfill/ (my preference but would require
LangVersion=latest
)? This would allow the library authors to use polyfilled language features even with Netstandard2.0.Those libs would also polyfill nullable annotations, which means the
Nullable
reference could be removed.Describe the solution you'd like
Using a Polyfilling library
Describe alternatives you've considered
Leaving as is
Additional context
No response
The text was updated successfully, but these errors were encountered: