Charles Milette

Because `IBindableIterable` doesn't implement `IIterable` despite having the same API surface :(

This could be fixed at the WinUI 3 level by having IBindableIterable do so, and should make the range-for and everything else just light up, but I assume the API...

I had to remove them because otherwise ```cpp using std::begin; begin(someWinrtType); ``` Would give conflicting overload errors, and I could not get ranges to work with cppwinrt's ADL begin... We...

Note that just adding those two methods back wouldn't work in some cases (e.g. trying to use IBindableIterator as a normal iterator wouldn't work).

For the custom main part yes, but not the message loop

Why not make it possible to do the initialization as a separate API call so that a consumer can simply call that, new up `Window`s, and run their own message...

Yep, sounds good to me

Bump? I'm thinking of introducing new features to my app which require custom message loop handling (specifically, using MsgWaitForMultipleObjectsEx and using an event to wake up the code to process...

Application.Run being blocking is a huge problem for me :(

Allowing custom message loops would probably be required to implement your feature proposal, but your proposal in specific isn't related to my use case (everything is contained within a single...