Patrick Meinecke

> Maybe I wasn't clear, but I meant that the `using module Alias = RealName` syntax was unimplemented and that I couldn't figure out what the original intent may have...

Centralizing all of the issues about inline splatting in #25721

> Feature request: make all of the numbers on the public objects settable The AST is immutable by design, allowing these properties to be set would be counter to that....

> Pretty please? @Jaykul Is your ask the same as it is in the OP or did it change with the information I provided? If it changed can you clarify...

Yeah makes sense. Something like this? ```diff public partial class ScriptExtent { + public ScriptExtent(IScriptPosition startPosition, IScriptPosition endPosition); } public partial class ScriptPosition { + public ScriptPosition( + string scriptName,...

The Engine WG discussed this and agree with my proposal above.

More specifically it was likely implemented for `ForEach-Object`, at least that's how it's most likely to be used today. ```powershell foreach ($a in $b) { $a | % { if...

This isn't a direct response to your request, but you can use `SteppablePipeline`s to invoke a command between blocks as if it were downstream. ```powershell function Set-Something { [CmdletBinding()] param...

> [@SeeminglyScience](https://github.com/SeeminglyScience) what do you think? @daxian-dbw Sounds good to me! I can't think of a use case

```powershell $Value = Get-Content -Raw $Function New-Item -Path function: -Name $Name -Value $Value -Force ``` FYI this would disable breakpoints from working correctly. I ask that you don't propagate things...