Patrick Meinecke

Yeah seems like an issue with the COM binder. It's probably not setting a binding restriction based on argument type. /cc @daxian-dbw

@daxian-dbw I think we just need to add the argument type to binding restrictions. Here's the code generated by the binder for when the argument is string. Note, the `if`...

Also related: #7651

The Engine-WG discussed this last night and we agree that casting should be aware of a few key interfaces and how to translate them. The big ones I can see...

I think a clear error message is probably the way to go here. A simple `Type.HasGenericParameters` check with a custom fail message.

> I don't feel strongly either way, but is your preference not to support this scenario more about how exotic it is, or are the performance concerns? I don't think...

> that's indeed how interfaces are reported via a type-info object's `.GetInterface(s)()` methods: The property `Type.Name` doesn't include generic parameters or arguments. `Type.FullName` will include them, and in this case...

> Good point, thanks for clearing that up. However, the point about it being true in an abstract, meaningful sense stands, as evidenced by the fact that you can _query_...

> Indeed. Just to clarify the [terminology](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/generics-and-attributes), you can query for an interface by the name of its _open_ generic type, i.e. a generic type whose type parameters haven't been...

> > that's just a PowerShell thing. > > The arity notation (e.g., `` IEnumerable`1 ``) is a language-agnostic _.NET API_ thing that PowerShell also (sensibly) happens to use -...