futures::Future trait implementation not available for IAsyncOperation<T> in v0.58 for some APIs

[qdot]

Summary

Trying to update to 0.58 in https://github.com/deviceplug/btleplug, now getting errors on all async calls to the WinRT Bluetooth APIs:

error[E0277]: `IAsyncOperation<GattCommunicationStatus>` is not a future
  --> src\winrtble\ble\characteristic.rs:72:32
   |
72 |         let result = operation.await?;
   |                               -^^^^^
   |                               ||
   |                               |`IAsyncOperation<GattCommunicationStatus>` is not a future
   |                               help: remove the `.await`
   |
   = help: the trait `futures::Future` is not implemented for `IAsyncOperation<GattCommunicationStatus>`, which is required by `IAsyncOperation<GattCommunicationStatus>: std::future::IntoFuture`
   = note: IAsyncOperation<GattCommunicationStatus> must be a future or must implement `IntoFuture` to be awaited
   = note: required for `IAsyncOperation<GattCommunicationStatus>` to implement `std::future::IntoFuture

I looked through the CHANGELOG but it's rather dense for this version update and I'm not sure what I'm missing.

Our last library version was released using v0.52, and updating to v0.57 still seems to work, it's just moving to v0.58 that seems to be causing this issue.

Crate manifest

No response

Crate code

No response

[kennykerr]

This was removed in #3142 out of safety concerns, but there is an attempt to bring it back in #3177.

[kennykerr]

Closing in favor of #342

[makepaddev]

I have the same problem, is this fixed now somehow? I can't seem to find a clear answer in all the related links. How do i get to call await?

[kennykerr]

Yes, this has been fixed as of #3213 - there just hasn't been a release of the windows crate with this update.

[makepaddev]

Ok. I've reverted to 0.56 in the meantime, also in 0.57/0.58 the 'implement' COM macro complains about core any not being available