Pierre Avital

Hello, Any updates on this? Sorry for being pushy, but most of rust-analyser's issues with type resolution point to this issue, I'd just like to see if there's any progress...

Thanks @jerry73204, we were planning to do something similar. We'd like to have the executor become an instantiable rather than a singleton, but this at least paves the way. I'm...

Hello, just wondering if there's any stable alternative to `Layout::array(n)` to allocate arrays manually right now ? This feature is the only block for me to switch my build to...

Closing this issue/PR, as the re-design has been done, in favour of the `SyncResolve` and `AsyncResolve` traits.

Hi, now that `stabby` is out, I'm eagerly awaiting accessors for the contents of the vtable and the date pointer, so that they may be passed over the ffi frontier...

Hi again, I've started a new RFC (https://github.com/rust-lang/rfcs/pull/3404) which, while orthogonal code-wise, has the same end-purpose of allowing the safe passage of wakers across the FFI. A key issue that...

> I had symbol clashes in the past when statically linking more plugins, to be checked if it is still the case. This is why the feature exists: when statically...

> Nice try! It looks like you miss sections "What is now impossible(or extremely complicated)" and "How new proposal solves this complications". Cheeky, I actually went and checked the template...

Indeed, this makes desugaring to RPIT impossible without adding a generic argument to the funciton. Ideally, it would desugar to `fn foo() -> impl for Future`, for this use of...

> > But to my knowledge, it is `fn foo() -> impl Trait` that desugars to `fn foo() -> AnonymousType` where `AnonymousType` can't be named, and only exposes the `Trait`...