Plecra

I'm having a look at good targets to reduce compile time in `-Z timings`. As always, `syn` is by far the worst offender. Any proc macro crates we can remove...

That sounds fantastic! I'll certainly give it a try because this sounds like it'd be useful for all sorts of rust work. What did this slow down looked like in...

uhh that's funny. it built just fine on my end

Has there been any consideration of `core::task::Context` in this API? It has a similar need for user-defined types, and (if they were added) would ideally use the same mechanism as...

Right. `Future`s are all tied to a specific reactor that manages their resources (Like sleeping and spawning other futures), and there have been a few proposals for giving them a...

As far as I'm aware, the `'static` restriction only applies to `TypeId` and `Any` as a consequence of them only using runtime checks. `Context` has its own lifetime that can...

That's pretty much it, yea! When trying to create the example, I hit the *small* snag that `Component` is an unsafe trait. The implementor basically has to ensure `transmute>()` is...

Hiya! Seems like this RFC has stalled a little - what's blocking progress at the moment?

> I wonder if it is possible to offload some of the complexity of this API to crates.io, similar to how `proc_macro` only exposes a basic interface (just a token...

The features only change the behavior of the `Backtrace` struct, right? I think just using the same documentation between the different implementations should be enough. It'd sidestep the problem of...