Michael Klement

To add to the list in the initial post: * #10669 and the closely related #20755

Another one to add to the list (a `using module` problem with referencing custom `class` definitions in the the `param(...)` block, specifically). * https://github.com/PowerShell/PowerShell/issues/19676#issuecomment-1555095799

Thanks, @anamnavi. I had assumed that the purpose of the property was the same. Good to know that these are now direct properties, but that doesn't seem to be the...

Thanks for writing this up. Re behavior 1. (resolving to full paths before creating the symlink): We do _not_ want this, because defining symlinks that reference their targets via _relative_...

If this gets fixed as suggested, the following is a moot point, but just to prevent additional confusion: #12797, which, as you state, was conceptually the wrong fix, only _partially_...

Thanks, @ca0abinary - that's the definitely the simplest option in v7.2+. I took the liberty of integrating your `Microsoft.PowerShell.ConsoleGuiTools` workaround into [this StackOverflow answer](https://stackoverflow.com/a/64232782/45375) (which is where the code in...

Per [about_Numeric_Literals](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Numeric_Literals#working-with-binary-or-hexadecimal-numbers): > If a binary string is some multiple of 8 bits long, the highest bit is treated as the sign bit. > [...] > Specifying an unsigned suffix...

I should have clarified that I was merely citing the documentation and showing a workaround, but let me weigh in on what I think of this behavior: It is certainly...

Thanks, @237dmitry; I think there are several actions needed: * The outright bugs described should be fixed. * The current behavior should be revisited, especially in light of the discrepancies...

@jhoneill, to set the stage for potential further discussion and to make it clearer where PowerShell "does its own thing": .NET and C# play by different, arguably better (simpler) rules:...