Olivier FAURE

I don't know about the other bug, but I was writing [`assert_let`](https://crates.io/crates/assert_let_bind).

> Is there any good reason why good() works but bad() does not work? Isn't this really just complex bug in rustc? If the return is Sized then could we...

@CAD97 > This seems problematic, as the guarantee is no longer a guarantee, as it doesn't apply in some cases That's a good question. On a specification level, GCE would...

@rpjohnst So if I'm understanding your proposed semantics, you're saying that `SomeType` would be treated as a contiguous block of memory when being passed to a function, and as a...

@kennytm There are pros and cons to using the generator syntax like you mention. On one hand, it's a little more concise; on the other hand, it requires keeping another...

> You are right about the ordering-- I didn't even consider that part. > > I guess that my main concern is the semantics of movement here. Assuming we omit...

@clarfon > be changed to: > > 1. Caller calls first half of `Box::new` > > 2. `Box::new` allocates memory, then yields to caller > > 3. Caller tells `f`...

@CAD97 > In fact, we could probably get away without actually doing anything special for Box::with to guarantee the copy elision on our side, and just ensure LLVM does it,...

@kennytm Thanks for the proof-reading. I think I've fixed all typos. I'm going to avoid using the `yield` syntax for now. @rpjohnst @comex I added details to the rationale to...

@rpjohnst Right. Re-reading our conversation, I think the main reason we've been talking past each other is that I've haven't been clear enough about NRVO. The way I see it,...