Docs: Uppercase or lowercase for Tuple property names?

[weitzhandler]

What is the convention for naming tuple properties?

(string Person, int Age)

or

(string person, int age)

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: dc229b53-a548-4ef8-86b9-58670a81344a
• Version Independent ID: aeb15230-e1cc-df50-7edb-fb50164e13be
• Content: What's New in C# 7.0 - C# Guide
• Content Source: docs/csharp/whats-new/csharp-7.md
• Product: dotnet-csharp
• GitHub Login: @BillWagner
• Microsoft Alias: wiwagn

[BillWagner]

That's a good question @weitzhandler

I don't know that we've addressed his in our own codebases. @jaredpar Is there an accepted practice for tuple member names and casing?

[jaredpar]

@terrajobst is driving the decision here. Not sure it's final final but the outcome is going to be that tuple names should be cased the same way you case property names.

[BillWagner]

Thanks @jaredpar

tuple names should be cased the same way you case property names.

@terrajobst If you're comfortably with that guidance, I'll add this issue to our "up for grabs" queue for community contributions.

[weitzhandler]

tuple names should be cased the same way you case property names

I'd vote for that to. Public members should be pascal cased. Would be nice to update this too.

[BillWagner]

Thanks folks. I've added this to the backlog, and added the "up for grabs" label.

[weitzhandler]

Actually not that simple.
Local variables might have different behavior. If you're going to make an official documentation about it, it should have clear rules.

For instance:

```c#
int x = 5, y = 10;

var t = (x, y);

x = t.x;
y = t.y;
```

[terrajobst]

The decision that we landed on is indeed PascalCase.

[SeanKilleen]

@BillWagner I went through the referenced doc and it appears all of the associated samples are in line with this naming convention guidance as far as I can tell.

Is there anywhere explicitly that you'd like this guidance added additionally? If not, this can likely be closed at this point.

[BillWagner]

Thanks @SeanKilleen

I'll close this.

Is there anywhere explicitly that you'd like this guidance added additionally? If not, this can likely be closed at this point.