Michael Klement

Good point, @PetSerAl - I was too narrowly focused on flat input collections. Do you agree that the `[object]`-based approach summarized by @vexx32 above is the best approach, given the...

@PetSerAl: While for `Get-Member` specifically (category A) it makes perfect sense for the behavior to differ, for the vast majority of cmdlets it does not, and - as argued in...

Good point, @ceztko. In fact, * https://github.com/PowerShell/PowerShell/issues/6291 is just one of several related bugs, which the following search surfaces ("Parameter parsing.passing" in the title, 8 issues as of this writing):...

Agreed re consistency, @kwkam. The larger issue, however, is that _output_ file paths should never have been treated as wildcards to begin with, which takes us back to #4726, #6729,...

Indeed this relates to the specific pasting method being employed: simulated typing (which breaks) vs. pasting the multi-line string as a whole, and the issue is being tracked in: *...

As an aside: It is a separate issue, but it is curious that parsing stops _after the comment line_ and considers the statement complete, given that it would make more...

I think the more relevant related issues are: * A partial duplicate, because in both cases what is between _escaped_ `[` and `]` is still inappropriately being treated as a...

@iSazonov, it's implied by @jhoneill's comment, but to spell it out: * On Unix, it absolutely makes sense, because you can have files literally named `a*b.txt` for instance (though it's...

Unlike `-Filter`, `-Include` and `-Exclude` use _PowerShell_ wildcards and therefore also support `[...]` constructs. > `dir -LiteralPath "profile.ps1" -Recurse` if `profile.ps1` isn't in the current dir., that is the expected...

> This is all harder than it needs to be :-( Amen to that. If backward compatibility weren't in the picture, I would eliminate the implicit recursion based on the...