René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Naming convention for local constants","articleBody":"Our [coding guidelines](https://github.com/PowerShell/PowerShell/blob/master/docs/dev-process/coding-guidelines.md#naming-conventions) the naming convention is to: \"Use `PascalCase to name constant local variables and fields.\" and is common with [dotnet repository guidelines](https://github.com/dotnet/runtime/blob/master/docs/coding-guidelines/coding-style.md).\r\n\r\nOn the other hand, the style for local constants is mostly `camelCase` in existing code so we should consider the logic for this part of our coding guidelines.\r\n\r\nIn https://github.com/PowerShell/PowerShell/pull/13217#discussion_r458263009 @rjmholt made a persuasive case we should use `camelCase` instead of `PascalCase` for local constants:\r\n\r\n\u003eMy thinking is that that's only for global constants (which behave most like value macros), rather than local constant variables (which can hold references and for which `const` indicates just immutability rather than referential transparency)\r\n\r\nIf we used `camelCase` for local constants this would be a violation of [SA1303ConstFieldNamesMustBeginWithUpperCaseLetter](https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1303.md) but there is an [open issue](https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/2082) as to whether the rule should apply to local constants as well as fields.\r\n\r\n\r\n\r\n\r\n\r\n","author":{"url":"https://github.com/xtqqczze","@type":"Person","name":"xtqqczze"},"datePublished":"2020-07-23T12:07:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":15},"url":"https://github.com/13247/PowerShell/issues/13247"}