Question on extra type casting to enable compilation

[greenozon]

Quick question: is it possible to somehow tell ILSpy during decompilation that certain casting is needed, otherwise it won't compile?

eg:

ILSPy decompiled some routine as follows, but it does not compile

and IL for it:

Original code looks like

[dgrunwald]

There's currently no option to force extra casts; we try to insert them only where needed.

ILSpy has its own C# compiler logic (CSharpResolver) that performs overload resolution and checks if writing a == b hits the correct comparison operator (if not, we'll insert casts). Looks like there's a bug in this particular case where our operator resolution logic believes that writing a == b ends up using the base class object == object comparison; but the C# compiler refuses to use any comparison (maybe it detects this as some kind of ambiguity?). -> Bug #3322