Private members in PowerShell classes about powershell-rfc

[KirkMunro]

The PowerShell team takes bug reports and enhancement requests on UserVoice now. You should post this over here instead and then close this issue: https://windowsserver.uservoice.com/forums/301869-powershell

[BrucePay]

I'm going to be marking this as closed. You can post on user voice or open up another RFC here. FWIW - we spent a lot of time talking about private members. Based on the fact that most of the successful scripting languages don't support private members, we didn't see a need to do this because it would make the debugger complicated. Currently the debugger is just a reentrant powershell session. If members were private in classes then they wouldn't be visible in the debugger without making unpleasant changes in the runtime. We did add a hidden attribute so members you don't want to display by default won't be shown which makes the formal signature of the class clearly visible.