Support for creating collections

[kennykerr]

Many APIs assume the caller will provide a collection of values. This should integrate with winrt::Param to allow regular Rust collections and iterators to bind to WinRT input parameters of WinRT collection types.

[kennykerr]

This depends on #81

[rookboom]

Many APIs assume the caller will provide a collection of values. This should integrate with winrt::Param to allow regular Rust collections and iterators to bind to WinRT input parameters of WinRT collection types.

Is there any workaround for this? I am trying to create a windows::ai::machine_learning::TensorFloat. It has a create2 constructor function which requires a Param<IIterable<i64>> as input .

Ideally I would like to call TensorFloat::create2([1,2,3]).
If I could create an IVector v somehow, I could maybe do something like TensorFloat::create2(v.get_view().into()) but the single_threaded_vector function does not seem to be available in Rust.

[kennykerr]

As a workaround, you can create a WinRT component with C++/WinRT that creates and returns the collection and then call that from Rust. You can even just have a component that returns an empty collection that you can then populate using Rust.

[riverar]

As a workaround, you can create a WinRT component with C++/WinRT that creates and returns the collection and then call that from Rust. [...]

Hey @kennykerr, is this still a current workaround? Just hit this myself, needing an IVector<IRandomAccessStream>.

[kennykerr]

Yes, this is still blocked on #81 where I need to add support to implement generic interfaces. Right now, the implement macro will only let you implement non-generic interfaces. I hope to get to this soon.