Jason Shirk

@SteveL-MSFT - my take on the RFC is that it is basically the same as defining your own function `TabExpansion` or `TabExpansion2`. That seems like the wrong approach to introduce...

I'm not sure we want non-collectible assemblies, but if you want to experiment, you can change `RunAndCollect` to `Run` [here](https://github.com/PowerShell/PowerShell/blob/cbe6b88df24297021d0eeb7864302e330d9c2c43/src/System.Management.Automation/engine/parser/PSType.cs#L1136).

It looks like an oversight, so I'll call it a bug.

This would resolve this longstanding issue too: https://github.com/PowerShell/PSReadLine/issues/579.

I believe supporting this is non-trivial. PSReadLine currently relies on `Console.ReadKey` to deal with the platform specifics w.r.t. input, e.g. on non-Windows, the dotnet runtime does a decent job of...

Coloring is token based, not tree based (an Ast is a tree), so you're really asking to color based on [TokenKind](https://github.com/PowerShell/PowerShell/blob/4af3068566b2218bc37ea19785ded589c2a5c42f/src/System.Management.Automation/engine/parser/token.cs#L18). I can't say I really like the idea (too...

You could and I considered that, but there is the small risk of collisions if PowerShell were to add a new token kind. Note that there are currently 5 allowed...

Possibly, I don't remember. I don't have V5 handy, just V5.1 and V6. If you check V5 and it matches the reference assembly, then I guess it's by design and...

To be clear here - my proposal was for parse time checks. Is the @PowerShell/powershell-committee thinking lexical checking should occur at runtime? Runtime checks have definite downsides: * Performance -...

Not exactly - you can edit the history file, but I think that would only take effect in new instances of PowerShell. This wouldn't be too hard to implement in...