Remove ExtensionAttribute from LinqBridge.cs #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removed the ExtensionAttribute definition from the namespace System.Runtime.CompilerServices. This causes `CS1685` warning when building on dotnet 10.0. This attribute should exist in `netstandard2.1` and `net4.5` target frameworks according to [documentation](https://learn.microsoft.com/en-us/dotnet/api/system.runtime.compilerservices.extensionattribute?view=net-10.0#applies-to). Only mono platform may missing this before net4.0, but that target framework is not in our list now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed the ExtensionAttribute definition from the namespace System.Runtime.CompilerServices.
This causes
CS1685warning when building on dotnet 10.0. This attribute should exist innetstandard2.1andnet4.5target frameworks according to documentation. Only mono platform may missing this before net4.0, but that target framework is not in our list now.Fixes: #24