Nika Layzell

I'm interested in how the analysis handles loops like this too. I've simplified the example a tiny bit and added comments to explain how it represents a use-after-free. I'm curious...

I threw together a simple macros 1.1-abuse crate which should generate code similar to the code which @jrmuizel posted above. It's super hacky but if you wrap it in a...

We'd need more APIs and ways to interact with the compiler. Currently we use a build script to collect all header includes and individual cpp! calls into C++ code which...

Unfortunately, I don't think that you can make custom crate-level attributes with proc_macro_attribute, as you can't import the macro to use it before the attribute needs to be resolved. I...

As I mention in that old comment, the `&mut` approach also requires a second lifetime, but it's hidden on the `&mut` itself. The original approach in the `object-provider` crate actually...

Adding something like `core::any::Request`, and making it's soundness require that it is only used by `Error` seems unfortunate to me, so I'd greatly prefer the `Pin` solution, even if we...

I actually wrote a branch for a potential `0.2.0` version of the `object-provider` crate which also uses `Pin` internally. I think there are a few behaviour differences between the two....

I've put together a (super rough) simplified version of the core idea behind the proposal in https://github.com/rust-lang/rfcs/pull/2895#issuecomment-739123333 here: https://github.com/mystor/dyno. The `Request` API which roughly maps to the existing `object_provider` crate...

In order to properly test the compiler's performance your best bet is probably to run the benchmark within a proc macro while compiling a dummy crate. The macro will be...

`Attribute` is one of the special cases for `parse_quote!` here: https://docs.rs/syn/1.0.38/syn/macro.parse_quote.html#special-cases. The normal `Parse` trait isn't used as usually when parsing you'll want to distinguish between wanting to parse an...