Add type-safe InvokeCommandSafe without ICommand overloads.

[HavenDV]

Now, when changing command parameters without explicitly specifying the types of arguments, the InvokeCommand (ICommand) overload is called, which ignores the input type and throws an exception only during runtime.

// this throws runtime exception
_ = Observable<Input>()
    .Select(_ => OtherTypeInput)
    .InvokeCommand(Command);

// this throws compile time exception
_ = Observable<Input>()
    .Select(_ => OtherTypeInput)
    .InvokeCommand<Input, Output>(Command);

// should throw compile time exception
_ = Observable<Input>()
    .Select(_ => OtherTypeInput)
    .InvokeCommandSafe(Command);

other suggested names: InvokeReactiveCommand

[HavenDV]

Or do it more radically and add a separate name for the ICommand overloads to avoid documentation problems.

[HavenDV]

A similar problem concerns the ReactiveCommand.Execute() method, which always has a no-argument overload. When changing command parameters from Unit to something new, a runtime exception is thrown, because an overload with no arguments is called. I would consider removing the empty overload (replacing it with ReactiveCommand.Execute(Unit.Default)), or creating a separate method to be explicitly called with arguments (ReactiveCommand.ExecuteWith(Unit.Default))

[ChadNedzlek]

Ugh. I just spent hours trying to track down this problem, because it causes an exception that I can't seem to catch. (the invoke command doesn't return anything useful I can observer for "it didn't even register right", and I can't seem to get the exception any other way)