Josh Triplett

@lebensterben We already have `obj.clone()`; the point of `obj.use` is that it *only* works for lightweight clones, not expensive ones.

@Lokathor wrote: > It might be better to have this as an attribute rather than yet another potential keyword position for parsing to deal with. Otherwise, great. I get that,...

@burdges wrote: > We've past proposals for inherent trait methods I think, mostly proposing a second inherent looking `impl` block, not sure that syntax matters, but this winds up functionally...

@bluebear94 Interesting! So, rather than requiring `unsafe impl Trait for Type`, you could implement the trait safely, as long as you don't override the method? That's a novel idea.

@programmerjake That's a great use case, thank you!

@scottmcm > If we're not adding pub() fn foo() {} and struct Foo { mut() a: i32 }, then I think any superficial similarity here is more harmful than good....

Canceling and restarting the FCP so that anyone who previously checked their box can decide if they still wish to do so with the new version that uses `final`. @rfcbot...

Would it be possible to get a gix-testtools release based on this? Also, is there some process that could avoid having gix-testtools get out of sync?

We discussed this in today's @rust-lang/libs-api meeting. We felt that this should not be exclusively a library value, because that wouldn't allow using it in `repr(align(...))`. This should have lang...

@BurntSushi Any thoughts or concerns about `replace_in_place` and `replacen_in_place`? @zachs18 If we added `replace_in_place` and `replacen_in_place`, do you feel your use case would still benefit from *also* having `replace_first` and...