Mathieu Guindon

icon indicating a website link https://www.rubberduckvba.com

icon location Québec, Canada icon location Microsoft MVP Alumni (Office Apps & Services, 2018-2022)

Results 234 comments of Mathieu Guindon

disable adding @Ignore comments into code

> Instead, I want to be able to ignore all occurrences across the entire > project or module without inserting any comments. I’m not referring to > disabling specific inspections...

disable adding @Ignore comments into code

> Currently, finding the option to set an inspection to DoNotShow by name under the settings is not straightforward. The UI does not anchor the action links from the bottom...

disable adding @Ignore comments into code

I changed the icon to a better-suited ❌ icon, but it instantly sets the inspection associated with the selected result, to `DoNotShow` severity, which disables it. I'll close this issue...

Inspection for collection/item returning function, where function(index) is faster than function.Item(index)

I think we'll end up with Excel-specific inspections in a dedicated `Rubberduck.Inspections.Excel.dll` assembly.

Inspection for redundant use of Exit Sub/Function/Property

I wonder if this should be part of something bigger, i.e. some "code is euristically unreachable" inspection.

Inspection for redundant use of Exit Sub/Function/Property

I'd want to flag redundant `Exit` instructions, but not only if they're the very last statement in a scope... and this requires code paths. let's keep this one for v3.

Inspection for duplicate/ambiguous public function names

TODO see if _ShadowedDeclaration_ picks it up already, otherwise this would be in scope for 2.x

Inspection for use of Resume not in Error handler

Prevents a run-time error that often confuses rookies and pasta chefs: > Resume without GoSub

For Each variable type should be as specific to the collection member type, where possible

*in early-bound code...

Inspection for redundant instruction separators

So, a parse tree inspection that finds: - instructions separator preceding the first instruction on a logical line of code (with or without a line number). - instruction separator following...