Patrick Meinecke

The Engine WG discussed this and agree that a better error message should be emitted.

@PaulHigin Out of curiosity, would you happen to know off the top of your head where to look for the code behind this behavior?

> Also, I think Patrick was looking at it earlier and the behaviour seems to persist for Invoke-Command Yeah seems to work the same way. > which is... problematic at...

> The argument is evaluated in the ScriptBlockToPowerShellConverter, while packaging the command to be sent over to the remote session. OHHHHHH okay that all makes sense now. To clarify, when...

> As for performance concerns: I haven't run tests, but I would expect the cost of maintaining an index to be negligible compared to the cost of invoking PowerShell code...

> As a user, I want to be able to mark modules as "never auto-import", which would require a programmer to use `Import-Module` in order to use it. Could you...

@iSazonov evaluating in chunks is a great idea ❤️ I'm less of a fan of just throwing it in another thread, since that gives the impression that the operation was...

@mklement0 > @iSazonov, do we already have cases of using .NET APIs that _do_ support cancellation that we _do_ surface via Ctrl-C? Yeah, that's essentially what `PSCmdlet.StopProcessing` is for. When...

Is there any reason why these changes wouldn't go into `ConsoleHost` instead of `Clear-Host`? The host can decide what to do with the current `SetBufferContents` even if it doesn't *really*...

@iSazonov All of the changes so far have made within the function `Clear-Host` itself instead of `ConsoleHost`. There may be a very good reason for this that I'm not aware...