Chandler Carruth

The leads discussed this, and I want to be clear we appreciate the feedback and considered this carefully. Ultimately, we would like to stick with the current design of `let`...

Just confirming that the leads are happy with the tweaked names here: https://github.com/carbon-language/carbon-lang/issues/1391#issuecomment-1185245169 Marking this as decided!

Just a quick reminder to not use specific issues to post more general feedback -- that should happen on its own discussion thread. Also, please keep feedback constructive.

> > Just a quick reminder to not use specific issues to post more general feedback -- that should happen on its own discussion thread. Also, please keep feedback constructive....

> Is `copy` really necessary to be part of the language? If `ref` is implicit for function parameters, and copies for rvalues, the following should work as well, shouldn't it?...

> This idea seems promising, and worth writing up as a proposal. We can't really. ;] It's dependent on another one. I'm going to try to fold this one into...

> @chandlerc Do you want an issue to track the need for a decision here, or are you comfortable saying that #821 should address this? Let's assume it will for...

Sorry this fell off folks radar... > about other questions? We expect to need something analogous to operator overloading to really retain the same kind of expressive library API capabilities...

> I agree with @chandlerc -- I see no concerns with adding this kind of feature, and it seems like useful functionality to support. We'll need to see a specific...

Also closing the issue for now. We can always re-open it if some aspect of the proposal ends up having concerns or controversy.