Daniel Henry-Mantilla

Haha, yeah I have been dealing with other projects 😅, I no longer had that much motivation for a crate that I didn't think much people were using (basically it's...

A tiny improvement _w.r.t._ footguns could be to: - maybe make the `if guard` mandatory for non-`FusedFuture`s - and/or some other way to express the intent that "I, as a...

Neat crate! I like it!! 🙂 Regarding https://cad97.github.io/pointer-utils/erasable/trait.ErasablePtr.html#safety, I think adding a counter example there would be helpful. It's kind of the same issue that the pin docs had for...

Thanks for reporting this, I was indeed unaware of this issue. A minimal reproduction of the problematic code emitted by nougat is, I believe: ```rust macro_rules! Where {( $T:ty :...

Now, generating something like: ```diff trait Trait : for + for + {} trait TraitItem : - 'a + for + + // if it were added, we'd have a...

I think the "chaining" would be automatically figured out, so I suspect that last theoretical example could just have `needs(Item)` on `Iterator` and `needs(Iterator)` on `DeepIterator` 🙂

For what is worth, since the api w.r.t. `F` is _ownership_-based exclusively (no `&` or `&mut` on the (value of type) `F`), it means covariance is necessarily fine 🙂

@douglas-raillard-arm a potential trick to make it not need a `SIZE`, which I suspect to be sound based on SB[^1] (but I don't know about TB[^2]), would be: ```rs #[repr(C)]...

Another alternative, for the specific case of `F` within `Lazy`, could be to hold it in a `ManuallyDrop` instead of a `Cell`. The sketch of this would be: - on...

> polonius-the-crap 😭 ___ Thanks for the report, I have to admit I was initially surprised the first time I noticed that `dyn for &'b T { convert::(x) } ```...