Patrick Meinecke
Patrick Meinecke
Mmmm tricky! I'm inclined to think that it should continue to infer the type on the RHS, but *only* of the closest assignment. But then if you do ```powershell [string]...
> 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...
FYI I haven't forgotten about this, I need some time to play around with it and see if any issues crop up
Yep! It's a known issue with `TabExpansion2`. Well, I don't know if there's an existing issue, but there's a bunch of commented code in `CommandCompletion.cs` where someone previously tried to...
The Engine WG discussed this, we think that `$PWD` is not the right solution (though we do agree this is a problem that needs solving). While it may often end...
The Engine WG discussed this PR and agree to the change but only if it's possible to avoid the behavior change (this is mostly a note to the reviewer, please...
The Engine WG discussed this and agree it's a bug that should be fixed.
Duplicate of #12533
Thanks for the report! We're tracking this in the issue above, consider giving it a thumbs up!
That's correct, it does inherit `hashtable`. While this particular instance can be controlled by PowerShell (since we explicitly changed it), it's worth noting that exact runtime type is almost always...