Geoff Romer

Do you still have this problem if you use a [homebrew installation](https://github.com/carbon-language/carbon-lang/blob/trunk/docs/project/contribution_tools.md#clang-and-llvm) of llvm instead of the apt-provided one?

> ...it will mean that `Optional(T)` is not a choice type (as claimed by the [error handling doc](https://github.com/carbon-language/carbon-lang/tree/trunk/docs/design#error-handling)), and so would require a more sophisticated design for pattern matching to...

> I suppose the `MatchContinuation` interface is somewhat magical in the sense that it its methods appear to have no implementation anywhere(?) The intent is that the compiler generates an...

Just to clear up one possible point of confusion: the `var Type:$$ ReturnType;` declaration inside `MatchContinuation` (sorry I called it `MatchInterface` earlier) would now be written `let ReturnType:! Type;`. It...

Can you explain a bit more about the purpose of this PR? In particular, does this make it easier for people to start contributing to the Carbon project, or only...

> ...it means programmers should always consider member packing/padding when creating their interfaces as opposed to optimising for readability. As you observed later in the thread, member packing/padding almost never...

We've been trying to avoid angle brackets because they create very serious parsing problems. For example, a correct C++ parser has to implement substantial parts of C++'s name lookup and...

The "Tail Calls" section of [this C++ proposal](https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1063r2.pdf) might also be a useful reference, if you'll pardon the self-citation. I personally agree that `tail return` is probably not the best...

> I was just wondering whether it was an explicit goal or non-goal to rule in or out a CFront-like thing. See the [interoperability goals](https://github.com/carbon-language/carbon-lang/blob/trunk/proposals/p0175.md) proposal: > The Carbon toolchain...

> I think it would be a great addition if we can specify class pointer and reference memory management strategy with the class declaration itself. > > Example: > >...