Add ChangeRefCellDerefToNotExpression code fixer #10469
Merged
Conversation
This file contains 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
|
This is ready for review. |
|
An alternative approach could be to nix the compiler API and just loop back through the range until a '!' is found. Simpler but maybe not technically pure |
KevinRansom
approved these changes
Nov 16, 2020
TIHan
approved these changes
Nov 17, 2020
|
re-opening because of nuget download failure in CI |
nosami
pushed a commit
to xamarin/visualfsharp
that referenced
this pull request
Feb 23, 2021
* Add ChangeRefCellDerefToNotExpression code fixer * Area
nosami
pushed a commit
to xamarin/visualfsharp
that referenced
this pull request
Jan 26, 2022
* Add ChangeRefCellDerefToNotExpression code fixer * Area
nosami
pushed a commit
to xamarin/visualfsharp
that referenced
this pull request
Jan 26, 2022
* Add ChangeRefCellDerefToNotExpression code fixer * Area
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Another common new user mistake - using
!to negate an expression, now with a quick fix to along with the improved error message: