[AST] emitLetToVarNoteIfSimple should also check if the method/accessor is explicitly non-mutating #27641
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.
emitLetToVarNoteIfSimple()
emits a diagnostic with a fix-it to addmutating
to a method or accessor. However, it's possible that the method or accessor is explicitlynonmutating
. In that case, we end up adding themutating
afternonmutating
, leading to another error:Method must not be declared both nonmutating and mutating
(if we have a method) orExpected 'get', 'set', 'willSet', or 'didSet' keyword to start an accessor definition
(if we have an accessor, like aset
).We should check whether we have an explicit
nonmutating
attribute and instead of inserting the fix-it, we should replacenonmutating
withmutating
.(I noticed when I was writing some tests!)