Chandler Carruth

It seems to me like this is *not* intending to be a duplicate of #1725 which is focusing on *removing* the distinction between `.Method()` on a pointer vs. a pointee....

First, a comment about the trailing `where` suggestion -- this is problematic as deduced types and parameters are needed within the signature of the explicit parameters and return, so it...

> There is precedent in Julia for defining type parameters after they're used with the `where` keyword, as opposed to just constraining parameters that were already defined (like in Rust),...

The leads went back over this and remain happy with member memory layout being in-order for now. You can see some of the rationale in my comment above: https://github.com/carbon-language/carbon-lang/issues/1680#issuecomment-1200079811 We...

After discussing, the leads decided "not right now". We can easily revisit this when we have (significantly) more experience with the current approach.

FWIW, I don't think there is really an issue to address here at this time. Our roadmap clearly lays out priorities and while we'd like to dig into build system...

> Switch to a different keyword without spelling concerns, such as `adapt` or `newtype`. If we can come up with a good different keyword, I'm all for it. But I...

Marking this as decided with "not now" based on the discussion with leads and the explanation from @zygoloid and @josh11b above.

Leads are ok with adding the title, and a pre-commit check to keep things consistent. Leads are ok with going to 6-digits at the same time. Want to write a...

Marking this as decided "yes" w/ @KateGregory's [update](https://github.com/carbon-language/carbon-lang/issues/1492#issuecomment-1465269337) for context, rationale, and the criteria.