Michael Hewson

@adetaylor based on your comments, it sounds like you understand what I was getting at with this example. In the case of `foo_cpp_ref.frobnicate_ref()`, there should be an error during type...

I just finished debugging a bunch of weird errors that ultimately was caused by this issue again — I must have forgotten to add the `.boxed()` workaround, and when I...

Referencing https://github.com/microsoft/TypeScript/issues/18122, because this is what is required for the example code there to work, and I can't comment there because it's closed locked.

> Yes Yes, as in you are planning on working on it / you know that someone is planning on working on it? I'm just asking because my next question:...

I guess what I would do here if I was writing a script like that would be to sleep for one second in between calls to `diesel migration generate`. Not...

An alternative that would solve both of the unresolved questions would be explicit `&move` references. We could have an explicit `alloca!` expression that returns `&move T`, and truly unsized types...

@eddyb I guess I can see why people think it's more ergonomic: in order to opt into it, you just have to add `?Sized` to your function signature, or in...

@eddyb have you seen @alercah's RFC for DerefMove? https://github.com/rust-lang/rfcs/pull/2439

@alexreg I would definitely appreciate your help, if I end up writing an RFC for `&move`. The idea I have so far is to treat unsized rvalues as a sort...

@alexreg >Has anyone specified the supposed semantics of &move yet, even informally? I don't think it's been formally specified. Informally, `&'a move T` is a reference that owns its `T`....