Raphael Taylor-Davies

Thank you for that context, very helpful :+1: From my perspective, the issue at the moment is that there is no way to detect a collision, and even if you...

So I had a look at implementing this but I'm not sure how to given the WebIdentityProvider is defined in rusoto_sts which has a transitive dependency on the rusoto_credential crate...

This would be especially useful when using Github Actions which for some inexplicable reason do not support passing command line arguments to services - https://github.com/orgs/community/discussions/26688

So I'll caveat all the below with the fact I'm relatively new to rust and so what I say may be incorrect, but following further experimentation I do not believe...

> If I had done this investigation, I would have stopped right here, unless I'd found an alternative to the borrowing. Experience has shown that this kind of borrowing is...

So one potential downside of moving the peripheral into the futures is that even the blocking APIs and usages can't borrow the values. The result is ``` let val =...

> as above, if the hal is futures-based the consumers will be pushed to be to, and drivers with buffers etc. are often not lightweight. it might be possible to...

@ryankurte I indeed meant the stabilization of async support in rustc, with both embedded support and the ability to use them in traits.

So the main problem I ran into when trying to do something similar in #149 was that as futures in rust are driven, the returned `Poll

@Nemo157 You are completely correct, I had a brain fart and conflated `Poll` and `impl Future`. GATs are only needed if trying to provide traits with methods that return futures....