-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modern framework support #749
Modern framework support #749
Conversation
8a715c9
to
b1dc561
Compare
@atifaziz @Orace I have released morelinq.temp as a proof of concept based on this branch. I have found this to improve compile-time compatibility while retaining run-time compatibility. This should be easier than using the I have checked .NET 5, and there are no changes to Please let me know if there are any issues with this solution. |
Codecov Report
@@ Coverage Diff @@
## master #749 +/- ##
==========================================
+ Coverage 87.90% 88.70% +0.79%
==========================================
Files 108 108
Lines 3473 3470 -3
Branches 984 978 -6
==========================================
+ Hits 3053 3078 +25
+ Misses 272 251 -21
+ Partials 148 141 -7
Continue to review full report at Codecov.
|
…upport # Conflicts: # MoreLinq.Test/MoreLinq.Test.csproj # MoreLinq/MoreLinq.csproj
I wonder if, instead of polluting the code with |
I could do it with a custom Fody weaver, but I would want to know that you guys are comfortable adding a dependency on Fody. That said, I think this is probably simpler than doing that, IMHO. A custom weaver would require an additional project and some work to identify the appropriate methods and strip the |
…upport # Conflicts: # MoreLinq.Test/MoreLinq.Test.csproj # bld/ExtensionsGenerator/Program.cs
Awaiting this eagerly. Anything holding it up? |
@atifaziz I've updated with build tests to future proof this. It will become more important with .net 6, which is adding several functions that will overlap with MoreLinq (dotnet/runtime#27687). |
@atifaziz - Updated to include .net6 support. Breaking change in |
I have released a preview version of a fork |
@viceroypenguin You should probably unfork it once you have no intention of merging into MoreLinq anymore. For starters, I'd want to file some issues 😉 |
If you want to help by filing some issues, please do! My initial focus was just on cleaning things up and putting a preview on nuget. I'd like to start copying some issues over and then start addressing them. |
@Arithmomaniac thanks for pointing that out - I turned the issues setting on. I like your issue, so please file it. Already thinking about how to start implementing long-term. |
Closing per comments in #565 and fork released via SuperLinq |
Properly implement solution for hiding extension methods on different frameworks by removing the
this
modifier.this
modifier can be removed and callers will still be able to reach the method.Fixes #738; improvement over #739