Patrick Meinecke
Patrick Meinecke
I looked into this a bit. The deserialized enum value is a `PSObject` whose `BaseObject` is the underlying value of the enum. For instance `[DayOfWeek]::Friday` would be a `PSObject` wrapped...
> This looks to me a bigger problem cross the board ... Yeah I didn't get into trying to explain how to fix that because I think it's even more...
> > ```powershell >> # These don't though. > > 10 + $sb > > 10 - $sb > > 10 / $sb > > 10 * $sb > >...
@daxian-dbw `PSGetEnumerableBinder` is another one. Not a huge deal obviously, but it would be neat if we could customize/define enumeration via ETS.
Centralizing all of the issues about inline splatting in #25721
Yep! https://github.com/PowerShell/PowerShell/pull/25552 https://github.com/PowerShell/PowerShell/pull/25548
The Engine WG discussed this, while we think this behavior is by design, we would like to add aliases to these engine intrinsic methods. Specifically, `PSForEach` for `ForEach` and `PSWhere`...
The Engine WG discussed this and agree we should make `ArgumentToEncodingTransformationAttribute` and `ArgumentEncodingCompletionsAttribute` public.
We discussed that but these are unlikely to conflict with anyone who created their own version, and we can always add a type accelerator later if desired.
Changes to modules that ship in Windows are typically done by their respective teams. Even when we're involved we generally don't have much say in how far back those changes...