Staffan Gustafsson

To give us a reasonable chance to help here, please read https://github.com/PowerShell/PowerShell/tree/master/tools/performance. Having a .etl file gives us much more to work with. GitHubPowerShell/tools/performance at master · PowerShell/PowerShellPowerShell for every...

As before, a performance recording would help, otherwise we are just guessing

Could you do something like this: ```powershell class ObjectGraphMethods{ static [System.Collections.Generic.IEnumerator[System.Management.Automation.PSPropertyInfo]] GetEnumerator([PSObject]$obj) { return $obj.Properties.GetEnumerator() } static [string[]] Keys([PSObject]$obj) { return $obj.psobject.Properties.Where{$_.Name -notin 'Keys', 'Values', 'Count'}.Name } static [object[]] Values([PSObject]$obj)...

I would prefer that it was the default :) That would make it consistent with ConvertFrom-Json and all the type system features that comes with PSObject would be readily available.

I wasn't aware of the yaml intricacies. Json is also in the same position regarding case sensitivity. In practice, it is rarely a problem. I can create a proxy command...

#25511 Adds alias PSForEach which can be used on List to work around this.

The Engine working group reviewed this and approved the idea, commenting that it needs to be reviewed by someone well-versed in the Crypt-API. Also, nice work @jborean93!

Seems like a valid concern! @SteveL-MSFT Do you have any recommendations for a code reviewer well-versed in the Crypt-API/Security Descriptors?

Here's a friendly reminder about `IArgumentCompleterFactory` and `ArgumentCompleterFactoryAttribute`. These can be used to create standard, parameterized completers.