René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Do not require { ... } (curly braces) around variable names for null-conditional member access","articleBody":"Note: This issue is just a reminder to reopen #11379 in order to have it revisited by the PowerShell committee; the willingness to do so was signaled in the Sept. '20 community call (see details below), but there was no follow-up, and leaving an issue in a closed state usually means that it falls through the cracks. There is clearly community interest in having this revisited, and the analysis that led to closing the issue is disputed.\r\n\r\nOnce #11379 is reopened, this issue can be closed.\r\n\r\n------\r\n\r\n@SteveL-MSFT \r\n\r\nThanks for discussing issue #11379 in the September community call (https://aka.ms/PSCommunityCall; as of this writing, the September call's recording has not been posted there, but is accessible at https://aka.ms/JoinPSCall, until the next call), starting at 46:00, based on @ThomasNieto's suggestion in the prior solicitation for discussion topics at   https://github.com/PowerShell/PowerShell-RFC/issues/260:\r\n\r\n(I was hoping to provide a direct link to the relevant portion of the recording, but that will have to wait until it is posted to YouTube and linked to at https://aka.ms/PSCommunityCall.)\r\n\r\nBased on your remarks in the recording:\r\n\r\n* Given that you indicated willingness to revisit this, please reopen the linked issue and re-tag it as `Review - Committee`.\r\n\r\n* As for your remarks that enclosing variable names in curly braces is a preexisting feature and that people object to having to use them in this case on _aesthetic_ grounds:\r\n\r\n  * I don't think anyone here _isn't_ aware that `{...}` _can_ and sometimes _must_ be used to disambiguate variable names.\r\n  * It is also not about _aesthetics_, it is primarily about _not getting the expected behavior_  in  manner that potentially _fails quietly_ (depending on what strict mode is in effect), due to _not expecting to have to use `{...}` in this case_; a secondary concern is typing inconvenience.\r\n\r\n\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2020-11-10T17:51:47.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":28},"url":"https://github.com/14025/PowerShell/issues/14025"}