Closed lue-bird closed 11 months ago
I think that for (f >> earlier) >> later
, we could simply have a fix that reports the parentheses. That would be a simplification in itself too.
If we do that, I think it could still make sense to improve our support/understanding of later << (f >> earlier)
, although a case could be made that the order should be made that that should be simplified. Though I don't think this rule should/could tell which composition operator should be preferred.
This is more a note to self for the future: Currently, only
inversesCompositionCheck
,toggleCompositionChecks
support reporting the first 2 inwith any combination of
>>
and<<
.In practice, this means adding
earlier.removeRange
,later.removeRange
toCompositionIntoChecks
and re-checking that the fixes work using these.Advantages
inversesCompositionCheck
andtoggleCompositionChecks
can be part ofcompositionIntoChecks
, something that has been bugging me