josh11b

> Seems that you guy misunderstand...carbon doesn't have `self` keyword, so `Me` is just a naming style, it doesn't matter... I have added `self` to the list of keywords in...

> You might consider splitting all the misc file changes to a separate PR in order to make it simpler to get feedback. Okay I will figure out how to...

> > You might consider splitting all the misc file changes to a separate PR in order to make it simpler to get feedback. > > Okay I will figure...

It is best not to change the wording of the proposals after they have been accepted. If it was just typo fixes that would probably be okay, but some of...

Carbon has a goal of being easy to parse for tooling, which has meant that we have considered and rejected angle brackets ``, due to experience with the difficulties parsing...

- I think `tail return` should require the implementation to perform tail-call elimination. It makes it easier to reason about, and making it an explicit in the source allows it...

@chandlerc Would you like to weigh in on the CFront-style transpiler is something we want to support?

Experience has shown that non-mutating should generally be the default: - Having fewer side effects means less need to alert readers that something dangerous or unexpected could be happening. -...

I've been thinking about this a little bit, and I wonder if something a bit more ad hoc might be appropriate for integer literals. In particular, I would like the...

In addition, this test passes, even though it should fail if type checking was happening correctly: https://github.com/carbon-language/carbon-lang/pull/1194/files#diff-0ffd162ea3936ac862435a58e53a61620f80e607da0bf38649526018ee65d56e Relevant code: ``` class Point(T:! Type) { // Should error, wrote `Point` instead...