-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Is it a useful change, to replace built-in types with keywords? #6917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it a useful change, to replace built-in types with keywords? #6917
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Docs Build status updates of commit 85436b2: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
It's best to open issue first if you want to submit a set of changes over multiple files or when you are not sure that changes will be accepted. See contributing guide: https://docs.microsoft.com/en-us/contribute/dotnet/dotnet-contribute
As for these changes, replacing type identifiers with language keywords is good, it was discussed recently here: dotnet/docs#24985 The system automatically pings the docs team, so your PR will be reviewed soon. |
That's exactly why I did NOT open a big PR. So this PR is more of a question, but phrased as a PR :). The problem is that this change alone might take tens or hundreds of PRs, so I'm a bit worried that you don't want it.
Right, but opening a PR immediately shows what I'm up to. I'm still a bit unsure whether it's good idea to fix so many things |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this @WhiteBlackGoose
I've reviewed these changes, and I'll now.
Thanks for the conversation @WhiteBlackGoose and @MSDN-WhiteKnight This is a good way to start, and over time, improving our samples is a goal. We'll continue to watch for and merge PRs that are roughly this size for these updates that bring our samples in line with our current stated coding standard. That said, reviews and merging may occasionally be delayed depending on release cycles (including preview releases). Thanks for understanding. |
I'm not spamming now. I'm trying to learn what's a good change and what is not worth reviewing. I didn't make this change before, so I need to know if I should make it. So far I know what I can do:
Please tell me if I should ping someone to review my PRs. Also, if this gets merged silently, would it be fair to consider this as "yes" to my initial question?