Michael Klement

Good point, @jhoneill: Given that the current binding of provider items via the pipeline happens by the `.PSPath` property value _only_, the _drive_ information is already lost by the time...

@iSazonov, a rewrite of the file-system provider will be most welcome, if and when it happens (the issue was created in 2018). In the meantime, it looks to me that...

@SteveL-MSFT, the larger issue here is that `Set-Location` should accept _any_ `[System.IO.DirectoryInfo]` instance piped to it and honor its PS drive information, if present, not just if emitted by `New-Item`....

On a side note, @LqkUWp: Please use the true names of PowerShell cmdlets in your issues, not aliases, especially if those aliases aren't defined on all platforms due to referring...

Your other example is the subject of: * https://github.com/PowerShell/PowerShell/issues/9475

Partitioning for the sake of _performance improvements_ via parallel processing of the partitions is definitely one important use of partitioning, but in this case I was thinking of partitioning for...

@iRon7,I think this ultimately comes down to the issue that you've already referenced in a previous comment: * https://github.com/PowerShell/PowerShell/issues/4242 In short, the speedup comes from passing all output as a...

Understood, @iRon7, but I fear that a solution is only feasible by: * (a) updating _individual cmdlets_ to make them do their own enumeration of collection-as-a-whole input * (b) clearly...

To summarize: * The chunking mechanism suggested in this issue is motivated by _business logic_, not performance. * However, with downstream cmdlets that support performing their own enumeration of collections...

That's an interesting idea, @dkaszews, but I'm unclear on the precise logic: What happens once the first empty line is hit (apart from emitting the previous batch)? Is the idea...