[Proposal] Allow Select Case to compare Object references

[VBAndCs]

This Code gives me a runtime exception, as it is assumed to use = in comparing the objects:

Select Case e.OriginalSource
   Case Me, Me.TexTBox
      cmb.IsDropDownOpen = Not cmb.IsDropDownOpen
End Select

So, this is Ok, but at least allow us to use Is. It is already used in some cases like Case Is < 10, but the next code is not accepted, and I think it should be:

Select Case e.OriginalSource
   Case Is Me, Is Me.TexTBox
      cmb.IsDropDownOpen = Not cmb.IsDropDownOpen
End Select

The only valid way is:

Select Case e.OriginalSource.GetType
  Case Me.GetType, Me.TexTBox.GetType
     cmb.IsDropDownOpen = Not cmb.IsDropDownOpen
End Select

Which is verbose and involving calling three methods!

[hartmair]

This problem is similar to #541. I'd be happy to see all this flavours of type matching be covered by a general pattern matching syntax like #367 so far.

[VBAndCs]

There is a difference. There I was comparing types, but here I am comparing references. In my use case, I could use the types instead of references because I am responding to an event that travels a specific route. This will not always be the case.

[AdamSpeight2008]

Select Case has other constructions.

Select Case True
       Case e.OriginalSource Is Me         : cmb.IsDropDownOpen = Not cmb.IsDropDownOpen
       Case e.OriginalSource Is Me.TexTBox : cmb.IsDropDownOpen = Not cmb.IsDropDownOpen
       Case Else Case Me, Me.TexTBox
End Select