Oli Scherer

There may be a simpler way. If I remember correctly, at some point all heap code in the standard library will be generic over the heap, although default that heap...

yes. I am working on https://github.com/rust-lang/const-eval/pull/43 that helps us organize which features depend on which other features. Once we have that we can discuss the roadmap for const features and...

That's a different topic (different as in, already applies right now and is orthogonal to heap allocations), and it only applies to the final value in a constant, not to...

As per the current design, you'd have a ```rust const fn new(a: A) -> YourType ``` and this is perfectly fine, we allow you to do that, even if you...

> That would be impossible because the pointer would contain an invalid address and validation would thus also fail. A good point. See more below > So once a constant...

There is no `const(heap)` effect anymore under the currently planned scheme. Everything is happening in the type system via an `impl const AllocRef for ConstAlloc`. I should have probably updated...

> I'm not sure how you're going to prevent pointers from escaping as usize unless you track every bit. well... we do that. you can't actually modify or read bits...

> The critical change required by this proposal is that pointer casting and pointer dereferencing must become const. They already are with a feature gate, you can explore this with...

Yea, sorry. My mental model of the internals of this probably do not reflect how it appears to work from the outside at all. In essense you can indeed say...

@gnzlbg gave us a great summary on irc. Here's the gist: * while it moved from LEWG to CWG and LWG, people had mixed feelings about it * basically, std...