MartinGC94
MartinGC94
I would call it user error. I'm by no means an expert in Generic types but from what I understand generics like `[System.Collections.Generic.Dictionary]` always require type arguments like `[System.Collections.Generic.Dictionary[string,int]]` if...
I only have 7.3 and 5.1 installed on my PC so I can't check if it's new in 7.3 or if it was added earlier but it looks like there's...
@mklement0 The problem with that approach is that every time a new option is added every interactive host author needs to update their app separately, and for editors that are...
I just use `New-Item -Force`. If it's there, nothing happens and if it's not then the command creates the folder. Note that this only applies to the filesystem provider, other...
`?` is a wildcard character, if I escape it, it works as I would expect: ``` PS C:\Users\Martin> Get-ChildItem -Path '\\`?\C:\Temp2' Directory: \\?\C:\Temp2 Mode LastWriteTime Length Name ---- ------------- ------...
@alanlivio Good news, according to the PS team blogpost: https://devblogs.microsoft.com/powershell/powershell-and-openssh-team-investments-for-2024/ one of the goals for 2024 is to focus on getting community PRs merged. Obviously they haven't started doing that...
So, apparently VisitAssignmentStatement returns whatever is on the left: https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/parser/TypeInferenceVisitor.cs#L977 This caused some issues in my first test `[string]$TestVar = "";[hashtable]$TestVar = @{};$TestVar` where the typeinference saw it like the...
> Doesn't this approach of reversing the order break this pattern of coding common to ps1 scripts? Not this exact scenario because parameters are handled before variable assignments, so it...
I found a simple solution, just add a special case for AssignmentStatements inside ParenExpressions. On a related note, do we have an official name for this: `$Var1 = ($Var2 =...
I've reverted the changes related to the assignmentstatementast type inference. I will (probably) look into fixing it in the future but it doesn't belong in this PR.