Oli Scherer

We removed all const trait impls and `~const` bounds from libcore, because it was blocking replacing the implementation with something maintainable. So at present we cannot add that, even for...

> so that all we guarantee is that `::eq` can be called in CTFE. It doesn't say anything about `PartialEq` itself. Is that right? Correct

I believe this is still entirely in the purview of the libs team. We may do an FCP of both teams on the first PR that adds this though.

oh 🤦 yea. We could pop all the current thread's frames and push the new thread's frames on thread switching. Could end up expensive, but only happens while you're logging,...

I don't think we can hijack that for our purposes, but I'll look into it.

I think this is the same issue as async tracing has https://github.com/davidbarsky/tracing-tree/issues/60 https://github.com/davidbarsky/tracing-tree/issues/74

We could generalize the `CString` optimization to a MIR optimization that finds any `!Copy` stored in temporaries that get a reference taken and end up with a raw pointer somewhere...

blocked on https://github.com/rust-lang/miri/issues/3397

bubbling up is something that should only show up in a special mode. Otherwise you can run `Vec::with_capacity(n)` with a binary search for the `n` to figure out the size...

note that `PAUSING` here doesn't mean that the span is exited temporarily. We're still in the span, we just additionally opened a new span nested within the outer span. ```...