More tests for Obsolete attribute to validate existing behaviour #13685
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
edgarfgp
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds adds unit tests that validates the current
[<Obsolete("", true>]>behaviour .Related issues that been raised based in a inconsistent compiler warning/error :
Obsolete warning isn't produced for some obsolete symbol usages #13511
Obsolete attribute is ignored in constructor property assignment #11868
Attribute defined on second method of property is ignored #11529
Compiler ignores obsolete attribute for enum cases. #6628
Using obsolete record field makes whole record construction expression obsolete #6370
Obsolete Attribute on AutoOpen Modules #1391