Simplify for optional value types

[kennykerr]

WinRT uses IReference<T> parameter and field types to indicate that a given argument/value is optional. This should be expressed in Rust using Option<T>. In particular, we should add Param specializations (as we do for strings) for IReference<T> input parameters to allow parameters to either accept T or None.

This builds on #92.

[kennykerr]

Closing this old issue - doesn't seem to be much demand for such API support. Let me know if you have thoughts to the contrary. 😊

[kennykerr]

Reopening as there's renewed demand for WinRT type system support. Doing what I described here #2310 (comment) should be a little easier with a stock implementation.

[kennykerr]

I think that IReference<T> support can be limited to "optional" behavior rather than the double mean used by Xaml and .NET for polymorphic value types. That simplifies the implementation and lets us treat IReference<T> more uniformly in Rust as semantically equivalent to Option<T>. The bindings can then be simplified to model IReference<T> properties as Option getters and setters rather than Param<IReference<T>> and Result<IReference<T>> respectively.

[kojiishi]

I was looking into how to call ToastNotification::SetExpirationTime.

After some try and errors, this seems to work:

let dt_obj: IInspectable = PropertyValue::CreateDateTime(dt)?;
let dt_ref: IReference<winapi::DateTime> = dt_obj.cast()?;
notification.SetExpirationTime(&dt_ref)?;

Great if this becomes easier to figure out.