Allow a program driving ILSpy.Decompilation to provide variable names during decompilation about ilspy

[dgrunwald]

There's already an interface IDebugInfoProvider intended for proving pluggable support for debug information (e.g. different .pdb file readers). This includes the functionality to provide variable names for local slots via the TryGetName method.

[Velociraptor115]

That is what I used initially
However, it doesn't cover StackSlot variables - the intermediate variables introduced by ILSpy for the sake of readability
What I'm describing is a way to extend or hook into the name generation part, rather than a mapping of locals to variable names

[Velociraptor115]

I have noticed a related issue
The variable name generation in ILSpy.Decompilation performs name collision checks on the entire method, I assume for performance and simplicity reasons.

For the reasons stated initially in this thread, long methods result in loop index variables, loop enumerator variables, and similar limited scope variables having unnecessary number suffixes appended to them.

Would modifying the logic to perform scope-based name collision detection be a good enhancement to ILSpy.Decompilation in general?