Mathieu Guindon
Mathieu Guindon
Probably easier to do in v3, but should be implementable in 2.x
Types _can_ be mismatched, if `Is` is used to determine whether an object implements a given interface. We should be able to warn about a "suspicious type check", given RD...
Similar to linked issue: should be easier in v3, but would probably be feasible in 2.x
I think we're starting to have enough material to introduce a `InspectionType.Performance` here. That's a good one BTW.
I think `IllegalAnnotationInspection` should be tweaked to pick these up, so we can report the problem before the attribute is even added to the member. Then yeah, there's still a...
Isn't this also applicable to any `Print` statement? i.e. can consecutive semicolons in a `Print#` statement be "collapsed" into a single one without affecting the output? If that's the case...
Sounds like some `DiscardedObjectReferenceInspection` could encompass both, no? Plus these: ```vb Workbooks.Add '
Absolutely! This has been annoying me for a while...
@ThunderFrame that's more complex, it involves *adding* a `With` block - here it would be seeing that there's *already* a `With` block in place. But that would be a very...
Given there's no compile error with `Set foo = New Workbook`, I like the inspection... but I don't think the quickfixes would be realistic, there's just too many edge cases....